nALFS Hackers Guide: Version 20031110 | ||
---|---|---|
Prev | Chapter 2. General Information |
When you are ready to produce a tarball for distribution, there are a few steps to follow:
Check out a clean copy of the nALFS repository. Using an existing copy, especially one that has been configured and used as a build tree, can potentially cause errors in the make dist process.
Edit bootstrap.configure, and modify the line starting with AC_INIT to reflect the version number that you want the distribution to be given (replace "CVS" with your desired version number). Do not commit this change to the CVS repository, as the CVS version should always report its version number as "CVS".
Run sh ./bootstrap -d CVS -g CVS -p 5.0. This command will create the configure script and Makefile (as is normally done with a CVS checkout), but will also download, extract and rename the documentation files that will be included in the tarball. These files include the DTD (the current CVS version), the syntax document describing the DTD, the user's guide and the hacker's guide. The latter three documents are currently downloaded from James Robertson's home directory on the LFS server, but see the URL_BASE variable in the bootstrap script to change the download source. In addition, the LFS-5.0 profile will be downloaded so it can be included in the tarball.
Run ./configure specifying any parameters your system needs to complete the configuration process.
Run make dist. This will produce both a .tar.gz and a .tar.bz2 file in the current directory containing everything that should be needed to build nALFS on an end-user's system. Note that this tarball will be created using the autoconf, automake and libtool versions on your development system, so please make sure they are current releases before creating a tarball for public consumption.
Run make distcheck. If your system requires any special parameters to be given to configure for it to complete (like --with-libxml2, for example), then you can use make DISTCHECK_CONFIGURE_FLAGS="..." distcheck to supply those parameters. The distcheck process will actually unpack the tarball into a temporary directory, and run a complete configure/make/install/uninstall process on it to ensure that no build errors occur. This step should be considered to be mandatory before releasing your tarball to the general public.