| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Zac Medico wrote: |
| 5 |
> Hi everyone, |
| 6 |
> |
| 7 |
> This is a revised version of the PROPERTIES=set proposal which has |
| 8 |
> been discussed previously [1]. |
| 9 |
> |
| 10 |
< snip a detailed proposal about a new kind of set> |
| 11 |
|
| 12 |
Let me try show some real examples of the type of sets I would like to |
| 13 |
use and how I'd like to use them, so that your proposal and the |
| 14 |
discussion on sets can take this into account. |
| 15 |
|
| 16 |
"meta" sets: |
| 17 |
- ---- @kde ---- |
| 18 |
# We don't include kdesdk on the global set |
| 19 |
kde-base/kate |
| 20 |
|
| 21 |
@kdeadmin |
| 22 |
@kdeartwork |
| 23 |
@kdebase |
| 24 |
@kdeedu |
| 25 |
@kdegames |
| 26 |
@kdegraphics |
| 27 |
@kdemultimedia |
| 28 |
@kdenetwork |
| 29 |
@kdepim |
| 30 |
@kdetoys |
| 31 |
@kdeutils |
| 32 |
- ---- @kde ---- |
| 33 |
|
| 34 |
simple sets (list of ebuilds) |
| 35 |
- ---- @kdetoys ---- |
| 36 |
kde-base/amor |
| 37 |
kde-base/kteatime |
| 38 |
kde-base/ktux |
| 39 |
kde-base/kweather |
| 40 |
- ---- @kdetoys ---- |
| 41 |
|
| 42 |
sets with conditional deps |
| 43 |
- ---- @compiz-fusion ---- |
| 44 |
dev-python/compizconfig-python |
| 45 |
x11-apps/ccsm |
| 46 |
x11-apps/simple-ccsm |
| 47 |
x11-libs/compiz-bcop |
| 48 |
x11-libs/libcompizconfig |
| 49 |
x11-plugins/compiz-fusion-plugins-main |
| 50 |
x11-plugins/compiz-fusion-plugins-extra |
| 51 |
x11-themes/emerald-themes |
| 52 |
x11-wm/compiz |
| 53 |
emerald? (x11-wm/emerald ) |
| 54 |
gnome? ( x11-libs/compizconfig-backend-gconf ) |
| 55 |
kde? ( x11-libs/compizconfig-backend-kconfig ) |
| 56 |
unsupported? ( x11-plugins/compiz-fusion-plugins-unsupported ) |
| 57 |
- ---- @compiz-fusion ---- |
| 58 |
|
| 59 |
It would also be important to have versioned sets (depending on a slot, |
| 60 |
for example). Marius Mauch (genone) suggested a very interesting way to |
| 61 |
solve this by using a set config file (portage specific) that, as he |
| 62 |
stated, "should work if I got the syntax right from memory" [current |
| 63 |
Portage svn] (something similar to): |
| 64 |
|
| 65 |
- ---- sets.conf ---- |
| 66 |
[slot-4.1] |
| 67 |
class=dbapi.VariableSet |
| 68 |
variable=SLOT |
| 69 |
include=4.1 |
| 70 |
|
| 71 |
[kdebase] |
| 72 |
class=files.StaticFileSet |
| 73 |
filename=kdebase |
| 74 |
|
| 75 |
[kdebase-4.1] |
| 76 |
class=base.DummyPackageSet |
| 77 |
extend=kdebase |
| 78 |
intersect=slot-4.1 |
| 79 |
- ---- sets.conf ---- |
| 80 |
|
| 81 |
Being able to take advantage of use deps for packages would be a bonus: |
| 82 |
kde? ( |
| 83 |
x11-libs/compizconfig-backend-kconfig |
| 84 |
x11-wm/compiz[kde] |
| 85 |
) |
| 86 |
|
| 87 |
|
| 88 |
These type of sets cover what I need / would like to have at the moment. |
| 89 |
How would I like to use them? I would like to have the sets defined in |
| 90 |
the tree as "base" sets that users can "tweak" to their needs. So they |
| 91 |
should be able to use something similar to package.use (package.use |
| 92 |
itself?) to add desired conditional deps such as "@compiz-fusion |
| 93 |
- -emerald -gnome kde unsupported". With the sets operators being defined |
| 94 |
by genone for Portage[1] '-', '/' users should also be able to create |
| 95 |
sets with a list of packages they don't want to install, so if someone |
| 96 |
wouldn't want to install kppp with @kdenetwork, they could create a |
| 97 |
@kdenetwork-unwanted set with kppp and run "emerge -av |
| 98 |
@kdenetwork-@kdenetwork-unwanted". It would be really helpful if we |
| 99 |
could have a "package.mask" like structure that allowed users to "mask" |
| 100 |
deps from sets (does / could package.mask be used this way?) so that one |
| 101 |
wouldn't be forced to run "emerge -av @kdenetwork-@kdenetwork-unwanted" |
| 102 |
every time. Running "emerge -av @kdenetwork/@installed" to reinstall |
| 103 |
only installed deps or "emerge -uDav @kdenetwork/@installed" to update |
| 104 |
the existing deps are also interesting ideas. Perhaps we should start |
| 105 |
doing "emerge -uDav @world/@installed". |
| 106 |
|
| 107 |
Marius suggests the following for the subtraction issue (the same |
| 108 |
warning as above): |
| 109 |
- ---- sets.conf ---- |
| 110 |
# assuming @kdenetwork is already defined in a higher level sets.conf |
| 111 |
|
| 112 |
[kdenetwork-ignore] |
| 113 |
class=base.DummyPackageSet |
| 114 |
packages=kde-extra/i-dont-want-this |
| 115 |
|
| 116 |
[kdenetwork] |
| 117 |
remove=kdenetwork-ignore |
| 118 |
- ---- sets.conf ---- |
| 119 |
|
| 120 |
So this is what I would like to see with sets. Am I crazy? Is it |
| 121 |
possible to do any of this? Anyone has some other needs? |
| 122 |
|
| 123 |
- -- |
| 124 |
Regards, |
| 125 |
|
| 126 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 127 |
Gentoo- forums / Userrel / Devrel / SPARC / KDE |
| 128 |
|
| 129 |
[1] - |
| 130 |
http://planet.gentoo.org/developers/genone/2008/09/29/more_extensions_to_package_set_support |
| 131 |
-----BEGIN PGP SIGNATURE----- |
| 132 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 133 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 134 |
|
| 135 |
iEYEARECAAYFAkjm5yEACgkQcAWygvVEyAL6YwCZAaLiyKm8sUySAcgIgBdPDStT |
| 136 |
ZcQAn3+FGPlnmlxKPdKOkWQizs//vuKP |
| 137 |
=They |
| 138 |
-----END PGP SIGNATURE----- |
Archives