| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Sat, 12 Aug 2006 16:11:25 -0400 Alec Warner <antarus@g.o> |
| 3 |
> wrote: |
| 4 |
> | Ciaran McCreesh wrote: |
| 5 |
> | > On Sat, 12 Aug 2006 13:24:49 -0700 Zac Medico <zmedico@g.o> |
| 6 |
> | > wrote: |
| 7 |
> | > | Currently, portage only allows single inheritance in profiles, but |
| 8 |
> | > | it's easy to enable multiple inheritance. In order to do this, we |
| 9 |
> | > | only need to unconstrain the number of parents allowed in the |
| 10 |
> | > | parent file (only 1 is currently allowed). When a parent file |
| 11 |
> | > | contains multiple parents, parents listed later if the file will |
| 12 |
> | > | have the ability to override those listed earlier in the file. |
| 13 |
> | |
| 14 |
> | I still like Mixin's[1] with node deps ;) |
| 15 |
> |
| 16 |
> You can get the best of both worlds using straight MI, if the profile |
| 17 |
> tree is structured properly. Use the existing hierarchy for the 'main' |
| 18 |
> profile and mixins (nodes with no parent) as extras. The only problem |
| 19 |
> with this is Portage's current reliance upon a single symlink to |
| 20 |
> specify the profile... With Paludis one could do: |
| 21 |
> |
| 22 |
> profiles = default-linux/x86/2006.0 extra/x86/pentium4 extra/misc/cookie |
| 23 |
> |
| 24 |
> but with /etc/make.profile that's not an option... |
| 25 |
> |
| 26 |
|
| 27 |
Hmmm This sounds a lot more like what Kumba wanted than my original |
| 28 |
thoughts ;) |
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives