[Pkg-samba-maint] Library handling in the Samba 4.0 package

Ivo De Decker ivo.dedecker at ugent.be
Sun Sep 8 19:32:23 UTC 2013

On Sun, Sep 08, 2013 at 02:59:36PM +0100, Jelmer Vernooij wrote:
> > > It's clear that splitting the libraries will be very difficult. So if you
> > > think this is not realistic at this point, I don't mind if all the private
> > > libraries get merged into one big library package. Go for it!
> > Right, I'll move them all into a giant package in that case. What do
> > we want to do with the libraries that already live in separate
> > packages? They'll probably end up with circular dependencies on the
> > giant library package. I think it would be reasonable to keep them
> > with those circular dependencies for the moment, so we don't have to
> > remove and reintroduce them as we untangle the spaghetti.
> I've created a branch named "jelmer_integrate_libs" that adds a new
> samba-libs package and removes most of the library and libdev
> packages.
> The resulting samba-libs package is only a mere 3.8Mb for amd64, so
> not unreasonable I think.

After my latest changes, it's at 4.4 MB.

> libnetapi0 is the only old binary package now has a circular
> dependency on samba-libs; I think it might make sense to move it into
> samba-libs as well considering its nature (it uses pretty much every
> samba client library out there).

As I said in my other mail, I got more than that:

libnetapi0 libwbclient0 python-samba samba samba-common-bin samba-dsdb-modules samba-libs

I got it down to libnetapi0 samba-libs, which is what you mentioned. If there
is no external dependency on libnetapi0, it could be integrated as well.



More information about the Pkg-samba-maint mailing list