1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
3 <chapter id="Packaging">
6 <firstname>Jelmer</firstname><surname>Vernooij</surname>
10 <title>Notes to packagers</title>
13 <title>Versioning</title>
16 Please, please set the vendor version suffix and number in <filename>source/VERSION</filename> and call
17 <filename>source/script/mkvesion.sh</filename> to include the versioning of your package. There is also
18 the possibility to set a function to create the vendor version. This makes it easier to distinguish
19 standard samba builds from custom-build samba builds (distributions often patch packages). For example,
20 a good version would be:
23 <para><programlisting>
24 Version 2.999+3.0.alpha21-5 for Debian
25 </programlisting></para>
30 <title>Modules</title>
33 Samba has support for building parts of samba as plugins. This makes it possible to, for example,
34 put ldap or mysql support in a separate package, thus making it possible to have a normal samba package not
35 depending on ldap or mysql. To build as much parts of samba as a plugin, run:
39 The configure option <literal>--with-shared-modules</literal> is provided to
40 enable or disable specific modules such as idmap_XXX and vfs_XXX. For example,
41 <literal>--with-shared-modules=idmap_ad</literal>. Disabled modules are
42 prefixed with a '!'. E.g. <literal>--with-shared-modules='!idmap_ad'</literal>.
47 ./configure --with-shared-modules=rpc,vfs,auth,pdb,charset