| 1 |
Ühel kenal päeval, L, 04.02.2017 kell 07:26, kirjutas Mart Raudsepp: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> I am working towards having a clean deptree for arm64 and afterwards |
| 5 |
> marking the non-hardened 5 arm64 profiles stable (or 4 - I don't see |
| 6 |
> value in the developer profile without the desktop specific |
| 7 |
> subprofiles, until there are mix-ins). |
| 8 |
> |
| 9 |
> This e-mail is meant to make sure there are no other pre-requisites |
| 10 |
> for |
| 11 |
> just flipping the switch in profiles.desc from exp to stable, and to |
| 12 |
> express that intent and garner any hands-on help. |
| 13 |
|
| 14 |
Lots of concerns, I see from the zero replies so far :) |
| 15 |
To make it easier to handle new keywording that's happening earlier too |
| 16 |
in parallel, I now additionally plan to move half of these profiles |
| 17 |
from exp to dev in a couple of days, so that when repoman -d is used, |
| 18 |
it catches it, and when repoman -e y is used, it catches things too |
| 19 |
with the profiles that are left in exp for now. |
| 20 |
Moving from there to stable profile would not be done without the |
| 21 |
deptree fully clean, of course. |
| 22 |
|
| 23 |
Additionally there have been questions about stable keywords: |
| 24 |
|
| 25 |
I don't have short term personal plans on doing any new stable keywords |
| 26 |
until I'm done with having useful desktops in ~arm64. To get us towards |
| 27 |
stable _profiles_, I plan to use.stable.mask or package.use.stable.mask |
| 28 |
and so on as appropriate if possible, and only look into a stable |
| 29 |
chroot and stable keywording when that's not reasonable. |
| 30 |
|
| 31 |
Then afterwards yes, there is the intention to also have a bigger |
| 32 |
stable tree, but for me that's more like a 2-4 months timeline from now |
| 33 |
to even start there, depending on helping manpower and the capability |
| 34 |
to keep up. And also in the future I do want us to be a security |
| 35 |
supported architecture, given sufficient manpower and such. |
| 36 |
|
| 37 |
> Also some eyes on the profiles (profiles/arch/arm64/*) would be |
| 38 |
> useful, |
| 39 |
> especially from those who knows how all these CHOST/LIBDIR and other |
| 40 |
> things need to be, to make sure these are all right before the |
| 41 |
> profiles |
| 42 |
> go stable. |
| 43 |
> |
| 44 |
> |
| 45 |
> Currently my plan is to solve all the deptree issues by mostly stable |
| 46 |
> use masks where needed (the stage building stable keywords haven't |
| 47 |
> kept |
| 48 |
> the deptree in mind so far, just for what USE flags are enabled for |
| 49 |
> stage building), and keywording ~arm64 or |
| 50 |
> use.mask/package.use.mask'ing |
| 51 |
> to fix the ~arm64 deptree too (depending on if I want it keyworded |
| 52 |
> immediately, or delay for future consideration and fix the deptree by |
| 53 |
> use masks till then). |
| 54 |
> I'm having the CI hamsters spin for this at |
| 55 |
> https://github.com/gentoo/gentoo/pull/3622 |
| 56 |
> |
| 57 |
> Yes, there is quite some work to do, but this e-mail is meant to get |
| 58 |
> any necessary formalities out of the way in parallel, so we can get |
| 59 |
> the |
| 60 |
> switch flipped right after instead of discussing it then, and not |
| 61 |
> continue a chasing game due to repoman not telling to file a |
| 62 |
> KEYWORDREQ |
| 63 |
> for us for new deps. |
| 64 |
> |
| 65 |
> Note that there is no arm64 project as of yet, it's been worked on to |
| 66 |
> some capacity as part of arm project, which I believe to be a bit |
| 67 |
> confusing (albeit similar to ppc/ppc64), but also a bit daunting with |
| 68 |
> the arm4/5/6/7/vfp/neon/etc combination explosion stuff in arm32 land |
| 69 |
> (so I think it's good to have a clean break there with project |
| 70 |
> documentation pages, people involvement, etc). I haven't been able to |
| 71 |
> convince steev as of yet about this and haven't exercised any project |
| 72 |
> creation rights myself yet :D |
| 73 |
> |
| 74 |
> |
| 75 |
> Mart |
Archives