1 How to create SILC distributions
2 ================================
4 This document describes how to prepare SILC distributions in SILC source
5 tree and how to package distributions for releasing. This also defines
6 the procedure what one should do when distribution is created for
9 The distdir/ directory contains all distributions that can be created
10 from the source tree. The distdir/default cannot be packaged, it must
11 be used only for development.
14 Preparing distribution
15 ======================
17 To prepare a specific distribution with specific version for packaging,
20 autodist <name> <version>
22 Where the <name> is the distribution name. It is one of the distributions
23 that was defined in distdir/ directory. The <version> is the version of
24 the distribution that will be prepared. The version format is
25 major.minor.build, for example 0.9.10. Example:
27 autodist client 0.9.15
29 This prepares 'client' distribution of version 0.9.15. The package will
30 have the version 0.9.15 automatically.
33 Configuring and compiling the distribution
34 ==========================================
36 When you prepare the distribution for releasing you should configure the
37 distribution without any specific configuration options, hence just give
42 To compile the distribution, give command:
46 If you want you can clear the environment first with make clean command,
47 but this is not necessary.
50 Packaging the distribution
51 ==========================
53 After the distribution is prepared, configured and compiled it can be
54 packaged with the following commands:
59 The 'makedist --bzip2' creates the default 'tar.gz' and 'tar.bz2'
62 NOTE: Before giving this command, make sure that you do not have any of
63 the tests in the SILC source tree compiled. If they are the binaries
64 will be included in the distribution which is not allowed. The tests are
65 always located in the tests/ directory, for example lib/silccore/tests/.
66 The tests are not compiled by default, but if you compiled them by
67 yourself make sure you make clean them before creating the distribution.
69 NOTE: Same thing must be assured for silcer/ and tutorial/ sub
70 directories. Make sure they are not compiled and does not include any
71 extra files. If you haven't compiled them after the CVS checkout, they do
72 not include any extra files.
74 NOTE for 'toolkit' distribution: Running ./configure for toolkit
75 distribution is not necessary. Toolkit is packaged simply by giving
81 Before releasing the distribution
82 =================================
84 Before releasing the distribution the created distribution must be tagged
85 in the CVS so that it can be checkout at a later time, if needed. The tag
90 Where <name> is the distribution name and <version> is the version of the
91 distribution in following format: major_minor_build, for example 0_9_10.
96 To tag the distribution go to the root of the SILC CVS source tree and
97 give, for example, command:
99 cvs tag silc_client_0_9_15