| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
All, |
| 5 |
|
| 6 |
since there has been a lot of discussion lately about default use flags, |
| 7 |
I looked at the profiles and found the following: |
| 8 |
|
| 9 |
All of these use flags are in base/use.defaults. As I understand it, if |
| 10 |
the package listed with the flag in this file is installed on the |
| 11 |
system, the flag is automatically turned on. If that's true, why are |
| 12 |
they also listed in default-linux/x86/make.defaults? Wouldn't it be |
| 13 |
better to have them turned on automatically when the package that |
| 14 |
installs them is merged? |
| 15 |
|
| 16 |
arts cups eds emboss foomaticdb gnome kde nls opengl perl python tcpd X |
| 17 |
|
| 18 |
I also found the following flags in both places. The difference here is |
| 19 |
that the packages listed with these in base/use.defaults are libraries. |
| 20 |
Again, do these need to be listed in both places? I would think these |
| 21 |
don't need to be in base/use.defaults if we are going to allow the user |
| 22 |
to turn on/off support for them. |
| 23 |
|
| 24 |
alsa berkdb gdbm gif gpm gstreamer gtk imlib libwww mad mikmod motif ncurses ogg pam pdflib png qt readline sdl ssl vorbis zlib |
| 25 |
|
| 26 |
any thoughts? |
| 27 |
|
| 28 |
William |
| 29 |
|
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 32 |
|
| 33 |
iD8DBQFDEhJKblQW9DDEZTgRAlzaAKCc+sLiwCO6HCE+UUnOvrnhY7f4kwCgoqkx |
| 34 |
Xzz8eV610fWxhZ6ccQ+adZ4= |
| 35 |
=HC0T |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives