| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> On Sat, 27 Sep 2008 17:21:18 -0700 |
| 6 |
> Zac Medico <zmedico@g.o> wrote: |
| 7 |
> |
| 8 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 9 |
>> Hash: SHA1 |
| 10 |
>> |
| 11 |
>> Hi everyone, |
| 12 |
>> |
| 13 |
>> Please consider a PROPERTIES=set value that allows an ebuild to |
| 14 |
>> indicate that it should behave like a package set when selected on |
| 15 |
>> the command line. This is behavior is somewhat difficult to describe |
| 16 |
>> in words but the following example should be sufficient to convey |
| 17 |
>> the general idea. Consider a case where all of the kde-base/*-meta |
| 18 |
>> packages exhibit the "set" property, and these packages and their |
| 19 |
>> dependencies are currently installed. In such a case, the default |
| 20 |
>> behavior for a command such as `emerge kde-base/kde-meta` should be |
| 21 |
>> to reinstall the the selected kde-base/kde-meta ebuild and the set |
| 22 |
>> of packages which includes it's direct dependencies and it's |
| 23 |
>> recursive "set" dependencies. So, assuming that all USE flags are |
| 24 |
>> enabled for the selected kde-base/kde-meta ebuild, it would |
| 25 |
>> reinstall the direct dependencies of kdeartwork-meta, kdebase-meta, |
| 26 |
>> kdeedu-meta, kdegames-meta, kdegraphics-meta, kdemultimedia-meta, |
| 27 |
>> kdenetwork-meta, kdetoys-meta, kdeutils-meta, and |
| 28 |
>> kdeaccessibility-meta ebuilds. Similarly, the default behavior for a |
| 29 |
>> command such as `emerge --unmerge kde-base/kde-meta` would be to |
| 30 |
>> uninstall the same set of packages. |
| 31 |
> |
| 32 |
> I'm not convinced that this is a good idea if some packages suddenly |
| 33 |
> behave _vastly_ different than others (from a users POV) without any |
| 34 |
> clear indication (a -meta somewhere in the name IMO doesn't count). |
| 35 |
> |
| 36 |
> Maybe we can just create a PackageSet class that wraps a package though |
| 37 |
> to get the same behavior while keeping the two behaviors separated by |
| 38 |
> syntax. |
| 39 |
|
| 40 |
Some some sort of mapping of packages into sets space does seem |
| 41 |
better than changing the behavior of these packages other cases. |
| 42 |
However, PROPERTIES=set will still be useful for governing |
| 43 |
recursion, since recursion into dependencies is probably not desired |
| 44 |
for non-meta packages in the same sense that it might be desired for |
| 45 |
meta-packages. |
| 46 |
- -- |
| 47 |
Thanks, |
| 48 |
Zac |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 51 |
|
| 52 |
iEYEARECAAYFAkjfwg4ACgkQ/ejvha5XGaMkYACdF/uvOatcWaw1DsQkY/nBZ6RW |
| 53 |
N4YAn2VFsZztPLzHO6V6T9eQER4b2tO9 |
| 54 |
=z2qG |
| 55 |
-----END PGP SIGNATURE----- |
Archives