Lars Wendler schreef op vr 06-12-2013 om 16:24 [+0100]:
Hi list,
in [1] we got a bug where was pointed out that it is impossible to use
=net-fs/samba-4* on a system which has dev-libs/openssl[kerberos]
installed.
Long story short, samba-4 hard requires app-crypt/heimdal while
Hi list,
in [1] we got a bug where was pointed out that it is impossible to use
=net-fs/samba-4* on a system which has dev-libs/openssl[kerberos]
installed.
Long story short, samba-4 hard requires app-crypt/heimdal while
openssl[kerberos] hard requires app-crypt/mit-krb5. Of course both
packages
On 12/6/13, 7:24 AM, Lars Wendler wrote:
The bug reporter suggests to use bundled heimdal from samba-4 which I
would like to avoid if possible.
If anyone knows some better solution please speak up. It is highly
appreciated.
It sounds ugly, but I generally lean towards pragmatic solutions: +1
On Fri, Dec 6, 2013 at 3:24 PM, Lars Wendler polynomia...@gentoo.orgwrote:
The bug reporter suggests to use bundled heimdal from samba-4 which I
would like to avoid if possible.
If the libraries were to expose the symbols of the embedded heimdal, it
would solve the obvious build problem and
On 06/12/13 19:14, Paweł Hajdan, Jr. wrote:
Now for a better solution: make samba also work with MIT Kerberos, and
make OpenSSL work with Heimdal.
That's a big effort.
If we decide not to serve the bundled heimdal libraries, we can declare
samba4 server components and openssl[kerberos]
There's also another package which suffers the same problem,
sys-auth/sssd hard-requires mit-krb5 so it can't be used together with
samba4 as well.
--
Timo Gurr
