| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Suggestion: |
| 5 |
|
| 6 |
How about a field in ebuilds where the author can list USE variables the |
| 7 |
package provides support for? Not what USE variables a package uses, |
| 8 |
but what USE variables the package "exports." |
| 9 |
|
| 10 |
Example: |
| 11 |
|
| 12 |
The alsa ebuilds would advertise the fact that once installed, you need |
| 13 |
to put 'alsa' in your USE list to take full advantage of it. |
| 14 |
|
| 15 |
On installation, if you don't have 'alsa' in your USE variable, it could |
| 16 |
print a message suggesting to add it. |
| 17 |
|
| 18 |
This would also allow a separate tool to analyze your installed packages |
| 19 |
and find USE variables that you aren't using. |
| 20 |
|
| 21 |
(It's no fun to install a package but forget to add whatever variable to |
| 22 |
USE, and then later realize you have to recompile a bunch of packages.) |
| 23 |
|
| 24 |
- - Robert |
| 25 |
|
| 26 |
- -- |
| 27 |
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBB929E54 |
| 28 |
Key fingerprint = BEA9 490C D2B9 AD83 E88B 3148 3136 34E4 BB92 9E54 |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.0.7 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iD8DBQE9cu3gMTY05LuSnlQRAqpcAJ9eMKplRiXCRE4NyrRlMT24wQ3WKQCeLoJC |
| 34 |
Fbt/L6fQ8FPNlGF6B5d9NUs= |
| 35 |
=Pp/N |
| 36 |
-----END PGP SIGNATURE----- |
Archives