Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alt
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-alt@g.o
From: Markus Duft <mduft@g.o>
Subject: Re: [PREFIX] prefix keywords need to go (?)
Date: Wed, 25 Mar 2009 14:33:15 +0100
On Wed, 2009-03-25 at 11:44 +0100, Michael Haubenwallner wrote:
> On Wed, 2009-03-25 at 07:50 +0100, Markus Duft wrote:
> > On Wed, 2009-03-25 at 00:30 -0500, Jeremy Olexa wrote:
> > > Any other thoughts?
> > however i talked to haubi a while back about keywords. he for sure has
> > some more wise words to say :)
> LOL!
> But indeed, my brain cooks an idea for some time now - time to serve
> (thank you for the trigger!):


> Now I want to tell PM which ebuild-keywords to use for my
> distro-instance, where only 1. and 2. really would make sense (sample
> for non-Prefix):
>      1. 'amd64 hppa ~x86'
>      2. 'amd64 hppa ~mips ~ppc ~x86'
>      3. 'amd64 hppa ~mips ~ppc x86'
>      4. '~amd64 ~hppa ~mips ~ppc ~x86'
>      5. 'amd64 ~hppa ~mips ~ppc x86'
> This could be done by telling PM how to merge KEYWORDS and
> HAUBIDIST_KEYWORDS in etc/make.conf or profile/make.conf, like:
> where 'HAUBIDIST' maps to 'HAUBIDIST_KEYWORDS' and 'GENTOO' maps to
> This eventually also could apply for Gentoo Hardened, to not have that
> large list in package.mask, but HARDENED_KEYWORDS in the ebuilds, and
> Because both KEYWORDS and HARDENED_KEYWORDS would be in upstream ebuild,
> this also could work for HAUBIDIST in make.conf:
> For Prefix:
> We could have PREFIX_KEYWORDS in the maintree-ebuild, and for HAUBIDIST
> - when it is a Prefix distro - to have in make.conf:
> For the vanilla "Gentoo Prefix Distribution", this would mean to have:
> the vanilla "Gentoo Linux Distribution" would ship with:
> and the vanilla "Gentoo Hardened Linux Distribution" with:
> What else would be needed for the whole topic:
>       * helpers to manage/merge/update my private distro-tree.
>       * helpers to set up my private distro-mirror.
>       * repoman support for additional keyword variables
>       * ...

this whole proposal would fix multiple problems:

1) main and prefix keywords are different, but thats ok if prefix
keywords are PREFIX_KEYWORDS - we could do our own thing here.

2) it would solve the problem "how does portage know which packages can
i merge in a prefixed environment" - no need to trigger based on
inherit, EAPI - or something worse :)

3) it would ease porting to prefix: simply allow merging main ebeuilds
in prefix by adding GENTOO to the ACCEPT_DISTRO_KEYWORDS.

4) it would make gentoo a "real" meta distro as haubi said, since
gentoo's (linux or prefix) "consumers" can do their own thing with
keywords completely different from ours. it would be no problem to use -
for example - keywords like "mduft" and "haubi" (lol), as long as they

what about forwarding this thread to portage-dev@?

Cheers, Markus

> </braindump>
> Thoughts?
> /haubi/

Re: [PREFIX] prefix keywords need to go (?)
-- Jeremy Olexa
Re: [PREFIX] prefix keywords need to go (?)
-- Fabian Groffen
[PREFIX] prefix keywords need to go (?)
-- Jeremy Olexa
Re: [PREFIX] prefix keywords need to go (?)
-- Markus Duft
Re: [PREFIX] prefix keywords need to go (?)
-- Michael Haubenwallner
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [PREFIX] prefix keywords need to go (?)
Next by thread:
Re: [PREFIX] prefix keywords need to go (?)
Previous by date:
Re: [PREFIX] prefix keywords need to go (?)
Next by date:
Re: [PREFIX] prefix keywords need to go (?)

Updated Jun 17, 2009

Summary: Archive of the gentoo-alt mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.