| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
John Davis wrote: |
| 5 |
|
| 6 |
| Having GRP that is built with the defaults presented in the system |
| 7 |
| profile for critical packages is something that we should strive for. If |
| 8 |
| we make it very explicit that we *will* not offer support for cases when |
| 9 |
| this GRP was used on a non-default (default meaning they have not |
| 10 |
| modfied the profile use settings, cflags, etc), then I do not see the |
| 11 |
| problem. We have to keep in mind that users are NOT developers - they |
| 12 |
| don't do to their systems what we do to ours. To most users, vanilla |
| 13 |
| gentoo is just fine. If they decide that it is not, they discontinue use |
| 14 |
| of the GRP and simply emerge everything from source. |
| 15 |
|
| 16 |
By this time i may have had more than enough drinks, but wouldn't it be |
| 17 |
useful to handle a separate GRP profile? (or cascading profile). |
| 18 |
I mean, the basic profiles are skinny USE-wise and we (i) don't want to |
| 19 |
get them hogged... some source-building users mostly want to add stuff |
| 20 |
rather than remove, and it's logical. We should add some extras for GRPs |
| 21 |
somehow so they can get some goodies/features they lack because of the |
| 22 |
USE flags. |
| 23 |
Some simple examples could be "alsa", "ldap" or "ipv6". |
| 24 |
Just my $.02 |
| 25 |
Best regards. |
| 26 |
|
| 27 |
- -- |
| 28 |
Gustavo Zacarias |
| 29 |
Gentoo/SPARC & HPPA moncho |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 32 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 33 |
|
| 34 |
iD8DBQFAkGUCV3G/IBCn/JARAuPAAJ0XaMEbPi24A3SN5PEB1TEZo8jbqgCeOG3+ |
| 35 |
qf40OVG4WfKs746HeiHOxrs= |
| 36 |
=iqCf |
| 37 |
-----END PGP SIGNATURE----- |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-releng@g.o mailing list |
Archives