| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Zac Medico wrote: |
| 5 |
> Ryan Hill wrote: |
| 6 |
>> On Mon, 29 Sep 2008 22:31:46 -0700 |
| 7 |
>> Zac Medico <zmedico@g.o> wrote: |
| 8 |
> |
| 9 |
>>>> Can package.use syntax be extended to allow set entries? |
| 10 |
>>>> @compiz-fusion -gnome kde kde4 |
| 11 |
>>> Perhaps, but we need to clarify how that sort of setting will affect |
| 12 |
>>> nested sets. For example, if @compiz-fusion contains nested sets, |
| 13 |
>>> would those USE settings apply to the nested sets as well? Will |
| 14 |
>>> nested sets be allowed to have independent USE settings from the |
| 15 |
>>> sets that nest them? |
| 16 |
>> Maybe a nested set could inherit the USE flag settings of its parent set |
| 17 |
>> unless it has its own entry in package.use. |
| 18 |
> |
| 19 |
>> Though what happens if a package is in both sets which have |
| 20 |
>> conflicting flags in package.use? I would say that the nested set has |
| 21 |
>> to have priority. If not, I can easily imagine people getting confused |
| 22 |
>> when their USE settings for a set are being applied to all but |
| 23 |
>> one or two packages. |
| 24 |
> |
| 25 |
> It seems to me that the most logical approach would be to do some |
| 26 |
> sort of "incremental" stacking, similar to the way that USE flags |
| 27 |
> stack in the profiles. Suppose that we have the following settings |
| 28 |
> in package.use: |
| 29 |
> |
| 30 |
> @kde-meta foo bar |
| 31 |
> @kdeedu-meta -foo |
| 32 |
> |
| 33 |
> If the flags are stacked incrementally, analogously to the way that |
| 34 |
> they are stacked in profiles, then the above setting would apply the |
| 35 |
> "foo" and "bar" flags to all of @kde-meta except for the |
| 36 |
> @kdeedu-meta subset which would only have "bar" applied since "foo" |
| 37 |
> has been disabled incrementally. Does this approach seem reasonable? |
| 38 |
|
| 39 |
This sounds a good approach. |
| 40 |
|
| 41 |
Ryan, I disagree with your proposal. If I enable a use flag for the |
| 42 |
"meta" @kde and also disable it for @kdenetwork, I don't expect my |
| 43 |
option for the @kde "meta" to override my option for @kdenetwork. |
| 44 |
As Zac proposed, an incremental stack makes more sense. Before we had |
| 45 |
sets, when we enabled a use flag for a meta and disabled it for an |
| 46 |
ebuild pulled by the meta, we never expected the option for the ebuild |
| 47 |
to be overridden by the option for the meta. |
| 48 |
|
| 49 |
- -- |
| 50 |
Regards, |
| 51 |
|
| 52 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 53 |
Gentoo- forums / Userrel / Devrel / SPARC / KDE |
| 54 |
-----BEGIN PGP SIGNATURE----- |
| 55 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 56 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 57 |
|
| 58 |
iEYEARECAAYFAkjkN0kACgkQcAWygvVEyAK2iQCcDgNPwNlgw3MfV1WZj+S6L+xW |
| 59 |
RZ4An0UONUAt60WeQAUbDk2rEMduUub9 |
| 60 |
=VYib |
| 61 |
-----END PGP SIGNATURE----- |
Archives