<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc"> <chapter id="Packaging"> <chapterinfo> <author> <firstname>Jelmer</firstname><surname>Vernooij</surname> </author> </chapterinfo> <title>Notes to packagers</title> <sect1> <title>Versioning</title> <para> Please, please set the vendor version suffix and number in <filename>source/VERSION</filename> and call <filename>source/script/mkvesion.sh</filename> to include the versioning of your package. There is also the possibility to set a function to create the vendor version. This makes it easier to distinguish standard samba builds from custom-build samba builds (distributions often patch packages). For example, a good version would be: </para> <para><programlisting> Version 2.999+3.0.alpha21-5 for Debian </programlisting></para> </sect1> <sect1> <title>Modules</title> <para> Samba3 has support for building parts of samba as plugins. This makes it possible to, for example, put ldap or mysql support in a separate package, thus making it possible to have a normal samba package not depending on ldap or mysql. To build as much parts of samba as a plugin, run: </para> <para> The option <literal>--with-shared-modules</literal> is maintained to support specific modules such as idmap_XXX and vfs_XXX. For example, <literal>--with-shared-modules=idmap_ad</literal>. Use of this parameter to the <command>configure</command> command as not been supported in official releases. </para> <para> <programlisting> ./configure --with-shared-modules=rpc,vfs,auth,pdb,charset </programlisting> </para> </sect1> </chapter>