public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: multiple inheritance support for profiles
Date: Sat, 12 Aug 2006 16:33:57 -0400	[thread overview]
Message-ID: <44DE3B35.5050109@gentoo.org> (raw)
In-Reply-To: <20060812222408.1b51aad6@snowdrop.home>

Ciaran McCreesh wrote:
> On Sat, 12 Aug 2006 16:11:25 -0400 Alec Warner <antarus@gentoo.org>
> wrote:
> | Ciaran McCreesh wrote:
> | > On Sat, 12 Aug 2006 13:24:49 -0700 Zac Medico <zmedico@gentoo.org>
> | > wrote:
> | > | Currently, portage only allows single inheritance in profiles, but
> | > | it's easy to enable multiple inheritance.  In order to do this, we
> | > | only need to unconstrain the number of parents allowed in the
> | > | parent file (only 1 is currently allowed).  When a parent file
> | > | contains multiple parents, parents listed later if the file will
> | > | have the ability to override those listed earlier in the file.
> | 
> | I still like Mixin's[1] with node deps ;)
> 
> You can get the best of both worlds using straight MI, if the profile
> tree is structured properly. Use the existing hierarchy for the 'main'
> profile and mixins (nodes with no parent) as extras. The only problem
> with this is Portage's current reliance upon a single symlink to
> specify the profile... With Paludis one could do:
> 
> profiles = default-linux/x86/2006.0 extra/x86/pentium4 extra/misc/cookie
> 
> but with /etc/make.profile that's not an option...
> 

Hmmm This sounds a lot more like what Kumba wanted than my original 
thoughts ;)
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-12 21:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 20:24 [gentoo-dev] RFC: multiple inheritance support for profiles Zac Medico
2006-08-12 20:32 ` Ciaran McCreesh
2006-08-12 20:11   ` Alec Warner
2006-08-12 21:24     ` Ciaran McCreesh
2006-08-12 20:33       ` Alec Warner [this message]
2006-08-12 21:54         ` Andrew Gaffney
2006-08-12 22:02           ` Ciaran McCreesh
2006-08-12 22:37             ` Alec Warner
2006-08-13  1:07               ` Curtis Napier
2006-08-13  4:05           ` Kumba
2006-08-12 20:56   ` Zac Medico
2006-08-13  1:20 ` Brian Harring
2006-08-13  5:59   ` Zac Medico
2006-08-13  6:40     ` Brian Harring
2006-08-13 17:01     ` Alec Warner
2006-08-13 18:22       ` Marius Mauch
2006-08-13 19:54       ` Zac Medico
2006-08-13 19:14         ` Alec Warner
2006-08-14  0:21           ` Donnie Berkholz
2006-08-14 11:28             ` Alec Warner
2006-08-14 22:16               ` Christel Doty

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=44DE3B35.5050109@gentoo.org \
    --to=antarus@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