Hi as promised, I'm now on to tackle the Samba 4 package.
I've been studying the Fedora Samba 4 package [1], comparing with what we have right now in the gar recipe. The set of package Fedora rolls is substantially different to what we have and imo we should take a similar approach. 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 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). For reference, this is Fedora's set: samba4 samba4-client samba4-common samba4-dc samba4-dc-libs samba4-devel samba4-libs samba4-python samba4-pidl samba4-test samba4-winbind samba4-winbind-clients samba4-winbind-krb5-locator libsmbclient libsmbclient-devel libwbclient libwbclient-devel I propose the following changes to the Samba 4 recipe: o drop the 4 prefix, Fedora is considering the same [2]: "As samba4 is a superset of Samba 3 packages in Fedora, we are also considering to discuss renaming samba4 back to samba. As all existing API and ABI for smbd/nmbd/winbindd and libsmbclient library will be the same, the switch is not going to be problematic. However, there is still need to stabilize code through beta and pre-releases before doing that." o add the following packages: CSWsamba-common ... common files CSWsamba-lib ... Samba libraries CSWsamba-dc ... the new Samba 4 AD DC stuff CSWsamba-dc-libs ... libraries for CSWsamba-dc CSWlibtdb1 ... present in Samba 3, but missing in 4 CSWlibwbclient0 ... present in Samba 3, but missing in 4 CSWlibsmbclient0 ... present in Samba 3, but missing in 4 CSWlibsmbsharemodes0 ... present in Samba 3, but missing in 4 CSWsamba-nss-system-links ... present in Samba 3, but missing in 4 CSWsamba-pam-system-links ... present in Samba 3, but missing in 4 o drop the following packages: CSWlibnss-winbind1 ... obsoleted by CSWsamba4-wb-clients CSWlibnetapi0 ... unused CSWsamba4-swat ... SWAT is dead CSWsamba-nss ... merge content to CSWsamba-winbind The expactation is that users of the current Samba 3 package should be able to upgrade to Samba 4 in filesserver/NT DC mode without issues. Anyone who wants to run a AD DC must perform a manual setup as described in the Samba docs. There will be no support for auto-running the new samba AD controller process from init/SMF. Thoughts? -slow [1] <http://pkgs.fedoraproject.org/cgit/samba.git/tree/samba.spec> [2] <https://fedoraproject.org/wiki/Features/Samba4> _______________________________________________ maintainers mailing list maintainers@lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.