Re: [csw-maintainers] Samba 4, take 2, versioned packages
Hi Slow, Am 03.09.2013 um 16:43 schrieb slowfranklin slowfrank...@opencsw.org: I propose the following changes to the Samba 4 recipe: o package set: CSWsamba4 CSWsamba4-dc ... Samba 4 AD DC component, can be installed without CSWsamba4 CSWsamba4-client CSWsamba4-winbind... winbind stuff including NSS am PAM modules CSWsamba4-common ... common files CSWsamba4-libs ... Samba libraries CSWsamba4-dc-libs... Samba AD DC libraries CSWsamba4-nss-system-links CSWsamba4-pam-system-links o CSWlibwclient, CSWlibsmbsharemodes, CSWlibsmbclient and CSWlibnetapi will still be coming from Samba 3, Samba 4 will use private versions of these libs o the main package is split into libs and common, because it seems in Samba4 libraries like libsmbclient are linked with tons of private Samba libs, so we really want these private libs to be available as a seperate package otherwise the whole Samba packaged would be pulled in when someone installs libsmbclient o iirc running a Samba4 AD DC means you can't run the fileserver daemon smbd on the sambe host. For a AD DC you install CSWsamba4-dc, for a fileserver you install CSWsamba4. Nice and small packages. o no package CSWsamba4-swat, because SWAT is dead o no package CSWsamba4-dev, because we don't package any public library For reference, this is our current set for Samba 4: PACKAGES += CSWsamba4 PACKAGES += CSWsamba4-client PACKAGES += CSWlibnetapi0 ^^ PACKAGES += CSWlibnss-winbind1 PACKAGES += CSWsamba4-dev PACKAGES += CSWsamba4-swat PACKAGES += CSWsamba4-winbind These are the Samba 3 packages: PACKAGES += CSWsamba PACKAGES += CSWsamba-client PACKAGES += CSWlibsmbclient0 PACKAGES += CSWlibwbclient0 PACKAGES += CSWlibnetapi0 Are these two packages from Samba 4, Samba 3, or should they be in different pathes? PACKAGES += CSWlibsmbsharemodes0 PACKAGES += CSWlibtdb1 PACKAGES += CSWsamba-nss PACKAGES += CSWsamba-nss-system-links PACKAGES += CSWsamba-pam-system-links PACKAGES += CSWlibtevent0 PACKAGES += CSWsamba-dev PACKAGES += CSWsamba-swat PACKAGES += CSWsamba-winbind Only Samba 3 package consumed by other packages is CSWlibsmbclient0 (by CSWgnomevfs2 and CSWvlc). Best regards -- Dago -- You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process. - xkcd #896 smime.p7s Description: S/MIME cryptographic signature ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
Hi Dago Am 03.09.2013 um 16:46 schrieb Dagobert Michelsen d...@opencsw.org: Hi Slow, Am 03.09.2013 um 16:43 schrieb slowfranklin slowfrank...@opencsw.org: I propose the following changes to the Samba 4 recipe: o package set: CSWsamba4 CSWsamba4-dc ... Samba 4 AD DC component, can be installed without CSWsamba4 CSWsamba4-client CSWsamba4-winbind... winbind stuff including NSS am PAM modules CSWsamba4-common ... common files CSWsamba4-libs ... Samba libraries CSWsamba4-dc-libs... Samba AD DC libraries CSWsamba4-nss-system-links CSWsamba4-pam-system-links o CSWlibwclient, CSWlibsmbsharemodes, CSWlibsmbclient and CSWlibnetapi will still be coming from Samba 3, Samba 4 will use private versions of these libs o the main package is split into libs and common, because it seems in Samba4 libraries like libsmbclient are linked with tons of private Samba libs, so we really want these private libs to be available as a seperate package otherwise the whole Samba packaged would be pulled in when someone installs libsmbclient o iirc running a Samba4 AD DC means you can't run the fileserver daemon smbd on the sambe host. For a AD DC you install CSWsamba4-dc, for a fileserver you install CSWsamba4. Nice and small packages. o no package CSWsamba4-swat, because SWAT is dead o no package CSWsamba4-dev, because we don't package any public library For reference, this is our current set for Samba 4: PACKAGES += CSWsamba4 PACKAGES += CSWsamba4-client PACKAGES += CSWlibnetapi0 ^^ That is the current gar recipe which I'm going to modify, ie drop the libs. At the top of my mail I list the packages I would like to build from a modified Samba 4 gar recipe. PACKAGES += CSWlibnss-winbind1 PACKAGES += CSWsamba4-dev PACKAGES += CSWsamba4-swat PACKAGES += CSWsamba4-winbind These are the Samba 3 packages: PACKAGES += CSWsamba PACKAGES += CSWsamba-client PACKAGES += CSWlibsmbclient0 PACKAGES += CSWlibwbclient0 PACKAGES += CSWlibnetapi0 Are these two packages from Samba 4, Samba 3, or should they be in different pathes? For now, these libs will not be part of the Samba 4 packages. -slow ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
On 2013-09-03 4:43 PM, slowfranklin wrote: o CSWlibwclient, CSWlibsmbsharemodes, CSWlibsmbclient and CSWlibnetapi will still be coming from Samba 3, Samba 4 will use private versions of these libs I think you don't need libsmbclient, at all. Like you noted, only gnomevfs depends on it: no Samba binary uses it. So, no need for even a private one; libnetapi appears to be the same case. I see the Debian packages for v4 also have a libsmbclientraw, but that's apparently a different lib, since their libsmbclient (without raw) do switch from 3.6 to 4.0 in experimental. Do you see that one too? o the main package is split into libs and common, because it seems in Samba4 libraries like libsmbclient are linked with tons of private Samba libs, so we really want these private libs to be available as a seperate package otherwise the whole Samba packaged would be pulled in when someone installs libsmbclient Can you list them? I'm a bit surprised that this libsmbclient would have more dependencies, since it's supposed to be the same. Laurent. ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
o the main package is split into libs and common, because it seems in Samba4 libraries like libsmbclient are linked with tons of private Samba libs, so we really want these private libs to be available as a seperate package otherwise the whole Samba packaged would be pulled in when someone installs libsmbclient Can you list them? I'm a bit surprised that this libsmbclient would have more dependencies, since it's supposed to be the same. This is from git master HEAD, built on Solaris 11.1 with this simple configure invocation: $ ./configure \ --prefix=/opt/samba \ --with-ads \ --with-shared-modules=vfs_zfsacl fwiw, you also need the fix I attached to this PR: https://bugzilla.samba.org/show_bug.cgi?id=10112 As an alternative you can prefix the configure invocation with LDFLAGS=-RLIBDIR. -slow ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
Am 03.09.2013 um 19:05 schrieb Laurent Blume laur...@opencsw.org: On 2013-09-03 4:43 PM, slowfranklin wrote: o CSWlibwclient, CSWlibsmbsharemodes, CSWlibsmbclient and CSWlibnetapi will still be coming from Samba 3, Samba 4 will use private versions of these libs I think you don't need libsmbclient, at all. Like you noted, only gnomevfs depends on it: no Samba binary uses it. indeed. I'll see if they can be disabled in the build by configure. So, no need for even a private one; libnetapi appears to be the same case. I see the Debian packages for v4 also have a libsmbclientraw, but that's apparently a different lib, since their libsmbclient (without raw) do switch from 3.6 to 4.0 in experimental. Do you see that one too? Yes: $ ls /opt/samba/lib/libsmbclient-raw.so /opt/samba/lib/libsmbclient-raw.so o the main package is split into libs and common, because it seems in Samba4 libraries like libsmbclient are linked with tons of private Samba libs, so we really want these private libs to be available as a seperate package otherwise the whole Samba packaged would be pulled in when someone installs libsmbclient Can you list them? I'm a bit surprised that this libsmbclient would have more dependencies, since it's supposed to be the same. This is from git master HEAD, built on Solaris 11.1 with this simple configure invocation: $ ./configure \ --prefix=/opt/samba \ --with-ads \ --with-shared-modules=vfs_zfsacl slow@solaris:~$ ldd /opt/samba/lib/libwbclient.so | grep /opt/samba libwinbind-client.so = /opt/samba/lib/private/libwinbind-client.so libreplace.so = /opt/samba/lib/private/libreplace.so slow@solaris:~$ ldd /opt/samba/lib/libsmbclient.so | grep /opt/samba libsamba-util.so.0 =/opt/samba/lib/libsamba-util.so.0 libgssapi-samba4.so.2 = /opt/samba/lib/private/libgssapi-samba4.so.2 liblibsmb.so = /opt/samba/lib/private/liblibsmb.so libmsrpc3.so = /opt/samba/lib/private/libmsrpc3.so liblibcli_lsa3.so = /opt/samba/lib/private/liblibcli_lsa3.so libsamba-security.so = /opt/samba/lib/private/libsamba-security.so liberrors.so = /opt/samba/lib/private/liberrors.so libsmbconf.so.0 = /opt/samba/lib/libsmbconf.so.0 libtalloc.so.2 =/opt/samba/lib/private/libtalloc.so.2 libndr.so.0 = /opt/samba/lib/libndr.so.0 libcli_smb_common.so = /opt/samba/lib/private/libcli_smb_common.so libgse.so = /opt/samba/lib/private/libgse.so libutil_cmdline.so =/opt/samba/lib/private/libutil_cmdline.so libndr-standard.so.0 = /opt/samba/lib/libndr-standard.so.0 libdcerpc-samba.so =/opt/samba/lib/private/libdcerpc-samba.so libsmbregistry.so = /opt/samba/lib/private/libsmbregistry.so libsecrets3.so =/opt/samba/lib/private/libsecrets3.so libtevent.so.0 =/opt/samba/lib/private/libtevent.so.0 libutil_setid.so = /opt/samba/lib/private/libutil_setid.so libreplace.so = /opt/samba/lib/private/libreplace.so libkrb5-samba4.so.26 = /opt/samba/lib/private/libkrb5-samba4.so.26 libroken-samba4.so.19 = /opt/samba/lib/private/libroken-samba4.so.19 libasn1-samba4.so.8 = /opt/samba/lib/private/libasn1-samba4.so.8 libhcrypto-samba4.so.5 = /opt/samba/lib/private/libhcrypto-samba4.so.5 libcom_err-samba4.so.0 = /opt/samba/lib/private/libcom_err-samba4.so.0 libwind-samba4.so.0 = /opt/samba/lib/private/libwind-samba4.so.0 libheimbase-samba4.so.1 = /opt/samba/lib/private/libheimbase-samba4.so.1 libhx509-samba4.so.5 = /opt/samba/lib/private/libhx509-samba4.so.5 libwbclient.so.0 = /opt/samba/lib/libwbclient.so.0 libsamba-credentials.so.0 = /opt/samba/lib/libsamba-credentials.so.0 libndr-samba.so = /opt/samba/lib/private/libndr-samba.so libcli_cldap.so = /opt/samba/lib/private/libcli_cldap.so libcliauth.so = /opt/samba/lib/private/libcliauth.so libkrb5samba.so = /opt/samba/lib/private/libkrb5samba.so libsamba-sockets.so = /opt/samba/lib/private/libsamba-sockets.so libgensec.so.0 =/opt/samba/lib/libgensec.so.0 libasn1util.so =/opt/samba/lib/private/libasn1util.so libsamba-hostconfig.so.0 = /opt/samba/lib/libsamba-hostconfig.so.0 libndr-nbt.so.0 = /opt/samba/lib/libndr-nbt.so.0 libtevent-util.so.0 = /opt/samba/lib/libtevent-util.so.0 libsmb_transport.so = /opt/samba/lib/private/libsmb_transport.so libsamba3-util.so = /opt/samba/lib/private/libsamba3-util.so libCHARSET3.so =/opt/samba/lib/private/libCHARSET3.so libdcerpc-binding.so.0 =/opt/samba/lib/libdcerpc-binding.so.0 libndr-krb5pac.so.0 = /opt/samba/lib/libndr-krb5pac.so.0
Re: [csw-maintainers] Samba 4, take 2, versioned packages
slow@solaris:~$ ldd /opt/samba/lib/libsmbclient.so | grep /opt/samba libsamba-util.so.0 =/opt/samba/lib/libsamba-util.so.0 snip Okay, that's a lot, and really different. I gather you linked with -Bdirect? Of course not. :) Can you do ldd with -v to see if they're direct deps? http://pastebin.com/fJqGE4uh -slow ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
On 2013-09-03 7:18 PM, slowfranklin wrote: indeed. I'll see if they can be disabled in the build by configure. Don't bother too much if there's no option, just don't package them. It's maybe even better: when we switch to it, it'll have been built successfully many times over. Yes: $ ls /opt/samba/lib/libsmbclient-raw.so /opt/samba/lib/libsmbclient-raw.so Okay, so that one would deserve its own little CSWlibsmbclient-raw package. slow@solaris:~$ ldd /opt/samba/lib/libsmbclient.so | grep /opt/samba libsamba-util.so.0 =/opt/samba/lib/libsamba-util.so.0 snip Okay, that's a lot, and really different. I gather you linked with -Bdirect? Can you do ldd with -v to see if they're direct deps? I'm going to investigate in a vboxed Debian. Laurent ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
Re: [csw-maintainers] Samba 4, take 2, versioned packages
On 2013-09-03 7:49 PM, slowfranklin wrote: slow@solaris:~$ ldd /opt/samba/lib/libsmbclient.so | grep /opt/samba libsamba-util.so.0 =/opt/samba/lib/libsamba-util.so.0 snip Okay, that's a lot, and really different. I gather you linked with -Bdirect? Of course not. :) Give it a try? And -z nolazyload for good measure? Can you do ldd with -v to see if they're direct deps? http://pastebin.com/fJqGE4uh Really interesting. Most of those are stuffed into the python-samba package on Debian sid: http://packages.debian.org/sid/amd64/python-samba/filelist Then in experimental, they've been moved to other places, such as: http://packages.debian.org/experimental/amd64/libsmbd0/filelist And yet, their libsmbclient 4.0.8 (the one in experimental) does not depend on it that I can see, directly or not. There's something fishy. Laurent ___ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
