| 1 |
Groovy on the kerberos stuff! Finally someone else interested in it :) |
| 2 |
|
| 3 |
Quick thing.. why the skey use? And isn't kerberos 4 "outdated" now, so |
| 4 |
almost as if saying, "why bother" ? |
| 5 |
|
| 6 |
Dave Love said: |
| 7 |
<snip> |
| 8 |
|
| 9 |
> 3. I've then started adding new dependencies for the various |
| 10 |
> utilities, such as cyrus-sasl: |
| 11 |
> |
| 12 |
> dev/libs/cyrus-sasl/cyrus-sasl-1.5.27-r1.ebuild: |
| 13 |
> |
| 14 |
> DEPEND="... kerberos4? ( virtual/kerberos4 ) kerberos5? ( |
| 15 |
> virtual/kerberos5 )" |
| 16 |
> |
| 17 |
> src_compile() { |
| 18 |
> local myconf |
| 19 |
> use kerberos4 && myconf="${myconf} --enable-krb4" |
| 20 |
> use kerberos4 || myconf="${myconf} --disable-krb4" |
| 21 |
> use kerberos5 && myconf="${myconf} --enable-gssapi" |
| 22 |
> use kerberos5 || myconf="${myconf} --disable-gssapi" |
| 23 |
|
| 24 |
|
| 25 |
I think you might be able to shorten this to the use foo && bar || that, |
| 26 |
but probably kills the readability and might cause a line wrap *shrug*. |
| 27 |
BTW, with the above, I'm assuming you can have both kerberos 4 and 5 |
| 28 |
compiled into sasl (but I think I remember you cannot). |
| 29 |
|
| 30 |
|
| 31 |
> ... |
| 32 |
> |
| 33 |
> Am I on the right track here? It seems to work, but I want to |
| 34 |
> make certain I'm headed in the right direction before I go much |
| 35 |
> further. |
| 36 |
|
| 37 |
Looks like it. If kerberos 4 and 5 cannot coexist, then make a single |
| 38 |
virtual depend, or just don't do the virtual depend. |
| 39 |
|
| 40 |
jano |
Archives