| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> On Fri, 13 Oct 2006 02:40:59 -0700 |
| 6 |
> Zac Medico <zmedico@g.o> wrote: |
| 7 |
> |
| 8 |
>> At the profile level, I've added support for package.use |
| 9 |
>> which behaves like /etc/portage/package.use that everyone is familiar |
| 10 |
>> with. |
| 11 |
> |
| 12 |
> In a discussion about bug 151586 we realized that there might be an |
| 13 |
> issue with profile package.use. With the current stacking order |
| 14 |
> package.use in a profile will always override all make.defaults, |
| 15 |
> independent of the profiles they come from. In particular a parent |
| 16 |
> package.use can override a childs make.defaults USE. This doesn't |
| 17 |
> exactly match the existing profile semantics. |
| 18 |
> |
| 19 |
> Changing this however isn't trivial and would mean that in the |
| 20 |
> USE stack both files are treated as a single unit. |
| 21 |
|
| 22 |
That's a good point. I'll work on a patch to collapse make.defaults USE |
| 23 |
and package.use together at each level of the stacking process (and do the |
| 24 |
same for use.mask/package.use.mask). |
| 25 |
|
| 26 |
That means that USE_ORDER will be "env:pkg:conf:defaults:pkginternal", |
| 27 |
where the previous pkgprofile part has been merged with defaults. |
| 28 |
|
| 29 |
Zac |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 32 |
|
| 33 |
iD8DBQFFM+Xm/ejvha5XGaMRAllYAKDhyzqRwp5oSIO087+3cKYF4+6THgCdFZHk |
| 34 |
6hEO7OJZYRutlb3luqPxyao= |
| 35 |
=v/PQ |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives