This bug applies to: net-fs/coda/coda-6.0.10.ebuild net-fs/coda/coda-6.0.11.ebuild net-fs/coda/coda-6.0.12.ebuild It seems that the above ebuilds incorrectly support kerberos via the "kerberos" USE flag. When the USE flag is on, the ebuilds enable the "--with-crypto" flag to ./configure, when they should enable the "--with-krb5" flag. Note that the coda configure scripts for all of the above versions also support "--with-krb4" flags, which might be appropriate for the "krb4" USE flag.
Are you actively using coda? I am not using it myself anymore and I could use some feedback on how things are running to get an idea about the stability of the releases.
(In reply to comment #1) > Are you actively using coda? I am not using it myself anymore and I could use > some feedback on how things are running to get an idea about the stability of > the releases. > I am not actively using coda at the moment. I had hoped to assess its stability myself. I have talked to active users in contact with its maintainers at CMU, and both assert the stability of the system. Personal experience has shown that the configuration is atrociously difficult and requires intimate knowledge of technical details on behalf of both users and administrators, and the documentation is ancient enough to be downright incorrect. Problem-solving requires grepping through huge amounts of source, and occasionally manually inserting debug output in the code. The fact that it uses its own userspace thread library (lwp) and network library (rpc2) adds further complication. Stability aside, I do not recommend its use in any circumstance. :)
I added a coda-6.0.14 ebuild that should not suffer from this problem.
