[csw-maintainers] Samba 4, take 2, versioned packages

Dagobert Michelsen dam at opencsw.org
Tue Sep 3 16:46:00 CEST 2013


Hi Slow,

Am 03.09.2013 um 16:43 schrieb slowfranklin <slowfranklin at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2351 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20130903/9c62358c/attachment.p7s>


More information about the maintainers mailing list