| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Joseph Carter wrote: |
| 5 |
| Highly recommend that LDAP become non-optional for GnuPG since bascially |
| 6 |
| ALL HKP servers corrupt valid keys, the email servers don't support |
| 7 |
| OpenPGP, and the LDAP servers happen to actually work right, amazingly |
| 8 |
| enough. |
| 9 |
|
| 10 |
This leads me to an idea about USE variables. It may make sense for |
| 11 |
everyone to enable ldap for this one package but it doesn't make sense |
| 12 |
for everyone to add ldap to their USE variables. |
| 13 |
|
| 14 |
Also, making ldap support mandatory in a package goes against Gentoo and |
| 15 |
USE variable principles. |
| 16 |
|
| 17 |
My idea is to make the absence of a set USE variable not automatically |
| 18 |
mean "-var" but instead to make that mean the user is undecided and |
| 19 |
willing to accept default values on a package to package basis. |
| 20 |
|
| 21 |
The Gnupg ebuild would specify the default value for ldap as set. Then, |
| 22 |
one of three things will happen: |
| 23 |
|
| 24 |
A) User has "ldap" set in USE, enabling ldap support; |
| 25 |
|
| 26 |
B) User has "-ldap" set in USE, disabling ldap support; or |
| 27 |
|
| 28 |
C) User has no "ldap" set in USE, enabling ldap support via the default |
| 29 |
setting in the ebuild. |
| 30 |
|
| 31 |
If an ebuild does not specify a default, then it is taken to be disabled. |
| 32 |
|
| 33 |
- - Robert |
| 34 |
|
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v1.2.1 (GNU/Linux) |
| 37 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 38 |
|
| 39 |
iD8DBQE+LvOFbv6Y11NqSv8RAjFqAKCFgiGCpIWXfo4wl81JYPAj+kWc6QCeMlff |
| 40 |
Xyg9dHJebi+jPw7T5vZrBD0= |
| 41 |
=/SyM |
| 42 |
-----END PGP SIGNATURE----- |
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
gentoo-dev@g.o mailing list |
Archives