* Re: [gentoo-dev] RFC: Introducing stable profiles for arm64 (aarch64)
@ 2017-02-06 2:59 99% ` Mart Raudsepp
0 siblings, 0 replies; 1+ results
From: Mart Raudsepp @ 2017-02-06 2:59 UTC (permalink / raw
To: gentoo-dev
Ühel kenal päeval, L, 04.02.2017 kell 07:26, kirjutas Mart Raudsepp:
> Hello,
>
> I am working towards having a clean deptree for arm64 and afterwards
> marking the non-hardened 5 arm64 profiles stable (or 4 - I don't see
> value in the developer profile without the desktop specific
> subprofiles, until there are mix-ins).
>
> This e-mail is meant to make sure there are no other pre-requisites
> for
> just flipping the switch in profiles.desc from exp to stable, and to
> express that intent and garner any hands-on help.
Lots of concerns, I see from the zero replies so far :)
To make it easier to handle new keywording that's happening earlier too
in parallel, I now additionally plan to move half of these profiles
from exp to dev in a couple of days, so that when repoman -d is used,
it catches it, and when repoman -e y is used, it catches things too
with the profiles that are left in exp for now.
Moving from there to stable profile would not be done without the
deptree fully clean, of course.
Additionally there have been questions about stable keywords:
I don't have short term personal plans on doing any new stable keywords
until I'm done with having useful desktops in ~arm64. To get us towards
stable _profiles_, I plan to use.stable.mask or package.use.stable.mask
and so on as appropriate if possible, and only look into a stable
chroot and stable keywording when that's not reasonable.
Then afterwards yes, there is the intention to also have a bigger
stable tree, but for me that's more like a 2-4 months timeline from now
to even start there, depending on helping manpower and the capability
to keep up. And also in the future I do want us to be a security
supported architecture, given sufficient manpower and such.
> Also some eyes on the profiles (profiles/arch/arm64/*) would be
> useful,
> especially from those who knows how all these CHOST/LIBDIR and other
> things need to be, to make sure these are all right before the
> profiles
> go stable.
>
>
> Currently my plan is to solve all the deptree issues by mostly stable
> use masks where needed (the stage building stable keywords haven't
> kept
> the deptree in mind so far, just for what USE flags are enabled for
> stage building), and keywording ~arm64 or
> use.mask/package.use.mask'ing
> to fix the ~arm64 deptree too (depending on if I want it keyworded
> immediately, or delay for future consideration and fix the deptree by
> use masks till then).
> I'm having the CI hamsters spin for this at
> https://github.com/gentoo/gentoo/pull/3622
>
> Yes, there is quite some work to do, but this e-mail is meant to get
> any necessary formalities out of the way in parallel, so we can get
> the
> switch flipped right after instead of discussing it then, and not
> continue a chasing game due to repoman not telling to file a
> KEYWORDREQ
> for us for new deps.
>
> Note that there is no arm64 project as of yet, it's been worked on to
> some capacity as part of arm project, which I believe to be a bit
> confusing (albeit similar to ppc/ppc64), but also a bit daunting with
> the arm4/5/6/7/vfp/neon/etc combination explosion stuff in arm32 land
> (so I think it's good to have a clean break there with project
> documentation pages, people involvement, etc). I haven't been able to
> convince steev as of yet about this and haven't exercised any project
> creation rights myself yet :D
>
>
> Mart
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2017-02-04 5:26 [gentoo-dev] RFC: Introducing stable profiles for arm64 (aarch64) Mart Raudsepp
2017-02-06 2:59 99% ` Mart Raudsepp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox