Advise on the Samba4/OpenChange stack
 

I've been trying to package the OpenChange stack (OpenChange, Samba4 and
Heimdal) for Fedora, and I'm between a rock and a hard place on the
packaging of Heimdal (Samba's choice of Kerberos infrastructure). I can
either include it in Samba4 (as we do upstream), and break the 'no
included libraries' rule, or I can propose Heimdal as a package, and
conflict with krb5-devel and krb5-debuginfo.

Similarly, the non-library parts of Samba4 do conflict with Samba3.
(but I'm happy to simply not provide those parts of the package, if it
comes to it).

Does anybody have any suggestions about the best way forward?

The reviews are at:

https://bugzilla.redhat.com/show_bug.cgi?id=452212
https://bugzilla.redhat.com/show_bug.cgi?id=453083
https://bugzilla.redhat.com/show_bug.cgi?id=453395

Andrew Bartlett

--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
--
Fedora-packaging mailing list
Fedora-packaging@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging

Advise on the Samba4/OpenChange stack
 

Andrew Bartlett wrote:

I've been trying to package the OpenChange stack (OpenChange, Samba4 and
Heimdal) for Fedora, and I'm between a rock and a hard place on the
packaging of Heimdal (Samba's choice of Kerberos infrastructure). I can
either include it in Samba4 (as we do upstream), and break the 'no
included libraries' rule, or I can propose Heimdal as a package, and
conflict with krb5-devel and krb5-debuginfo.

Separate library packages. If it's just the -devel that's an issue,
placing Heimdal's headers in a subdirectory that samba4 can access by
using a -I/usr/include/heimdal, for instance, would work.



Similarly, the non-library parts of Samba4 do conflict with Samba3.
(but I'm happy to simply not provide those parts of the package, if it
comes to it).

Are Samba3 and Samba4 commandline compatible for these? If so it's
possible that alternatives is what we want to use here. These are the
criteria:


1) command line compatible
2) app that the sysadmin should deal with, not end users.

-Toshio

--
Fedora-packaging mailing list
Fedora-packaging@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging

Advise on the Samba4/OpenChange stack
 

On Wed, 2008-08-13 at 09:20 -0700, Toshio Kuratomi wrote:
> Andrew Bartlett wrote:
> > I've been trying to package the OpenChange stack (OpenChange, Samba4 and
> > Heimdal) for Fedora, and I'm between a rock and a hard place on the
> > packaging of Heimdal (Samba's choice of Kerberos infrastructure). I can
> > either include it in Samba4 (as we do upstream), and break the 'no
> > included libraries' rule, or I can propose Heimdal as a package, and
> > conflict with krb5-devel and krb5-debuginfo.
> >
> Separate library packages. If it's just the -devel that's an issue,
> placing Heimdal's headers in a subdirectory that samba4 can access by
> using a -I/usr/include/heimdal, for instance, would work.

Sadly it does not in reality. Having more than one kerberos
distribution's headers installed has been known to cause major pain,
even if the headers can be nominally separated.

> > Similarly, the non-library parts of Samba4 do conflict with Samba3.
> > (but I'm happy to simply not provide those parts of the package, if it
> > comes to it).
> >
> Are Samba3 and Samba4 commandline compatible for these? If so it's
> possible that alternatives is what we want to use here. These are the
> criteria:
>
> 1) command line compatible
> 2) app that the sysadmin should deal with, not end users.

No, they are not compatible.

Andrew Bartlett

--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc. http://redhat.com

--
Fedora-packaging mailing list
Fedora-packaging@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-packaging