From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new profile layout with flavors and mix-ins
Date: Wed, 02 Jul 2014 15:07:12 -0400 [thread overview]
Message-ID: <53B45860.2050400@gentoo.org> (raw)
In-Reply-To: <53B4523F.8040102@gentoo.org>
On 07/02/14 14:41, Rick "Zero_Chaos" Farina wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/02/2014 02:10 PM, Rich Freeman wrote:
>> On Wed, Jul 2, 2014 at 1:54 PM, Michał Górny <mgorny@gentoo.org> wrote:
>>> I don't feel like we ought to vote on something like this without
>>> understanding most of the current profiles. And I'm afraid there are
>>> only few people who have any idea about the current profile
>>> structure...
>> No argument there.
>>
>> We may very well still end up with something hierarchical, but we can
>> at least limit that to the parts of the profile where it matters.
>> Maybe x86/BSD and amd64/Linux and amd64/Linux-hardened need to be
>> interdependent. However, that still gets rid of need to deal with
>> desktop environments, init systems, arguments over what belongs in
>> @system, and so on. We could have a blocker mechanism to keep people
>> from mixing systemd with BSD, or we could just let people shoot
>> themselves in the foot.
>>
>> Sounds like a good time to start reverse engineering the profiles...
>>
> I've talked to the funtoo devs a few times about stealing their profile
> idea. A few things need to be done to make this happen, mainly eselect,
> catalyst, and repoman support. I can do the eselect and catalyst
> changes myself, however, I'll require some help for the repoman support
> most likely. I'll prototype this locally, see what I can make work, and
> then see about making it usable for others to test.
>
> - -Zero
> -----BEGIN PGP SIGNATURE-----
>
I don't know how to get from here to there. The problem isn't just
constructing an alternative profile tree. We could even have
/usr/portage/profiles-r2 and switch between the two on demand. The
problem is there's a lot of memory with flags and masks and these only
make sense in the context of the current stacking profiles.
Disentangling this information and bringing it over to profiles-r2 is
going to be work.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2014-07-02 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:44 [gentoo-dev] new profile layout with flavors and mix-ins William Hubbs
2014-07-02 17:54 ` Michał Górny
2014-07-02 18:10 ` Rich Freeman
2014-07-02 18:32 ` Anthony G. Basile
2014-07-02 18:35 ` Rich Freeman
2014-07-02 18:41 ` Rick "Zero_Chaos" Farina
2014-07-02 19:07 ` Anthony G. Basile [this message]
2014-07-02 19:19 ` Rick "Zero_Chaos" Farina
2014-07-02 19:30 ` Rich Freeman
2014-07-03 14:55 ` Andreas K. Huettel
2014-07-03 23:09 ` Tom Wijsman
2014-07-03 23:35 ` Rich Freeman
2014-07-03 6:18 ` Joshua Kinard
2014-07-03 7:00 ` Michael Haubenwallner
2014-07-03 8:47 ` Joshua Kinard
2014-07-03 16:06 ` Ian Stakenvicius
2014-07-03 8:53 ` [gentoo-dev] " Duncan
2014-07-03 9:01 ` Martin Vaeth
2014-07-03 7:32 ` [gentoo-dev] " Michał Górny
2014-07-03 8:21 ` Joshua Kinard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53B45860.2050400@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox