ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] Buildbot source tarballs

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxx>
Date: Thu, 31 Mar 2005 01:50:54 -0800
Anders Broman (AL/EAB) wrote:

I just realised that Buildbot source tarballs does not contain tools
or asn1 librarys - shouldn't they ?

Probably, although if somebody's going to be doing development to the extent that they need the tools or ASN.1 files, they might want to consider using anonymous SVN (which I think is easier to use through a firewall than was the old anonymous CVS, as I think it's just based on HTTP, which firewalls tend not to block).

The current automake documentation says:

	What Goes in a Distribution

	Basics of distribution

The dist target in the generated Makefile.in can be used to generate a gzip'd tar file and other flavors of archive for distribution. The files is named based on the PACKAGE and VERSION variables defined by AM_INIT_AUTOMAKE (see Macros); more precisely the gzip'd tar file is named package-version.tar.gz. You can use the make variable GZIP_ENV to control how gzip is run. The default setting is --best.

For the most part, the files to distribute are automatically found by Automake: all source files are automatically included in a distribution, as are all Makefile.ams and Makefile.ins. Automake also has a built-in list of commonly used files which are automatically included if they are found in the current directory (either physically, or as the target of a Makefile.am rule). This list is printed by automake --help. Also, files which are read by configure (i.e. the source files corresponding to the files specified in various Autoconf macros such as AC_CONFIG_FILES and siblings) are automatically distributed. Helper scripts installed with automake --add-missing are also distributed.

Still, sometimes there are files which must be distributed, but which are not covered in the automatic rules. These files should be listed in the EXTRA_DIST variable. You can mention files from subdirectories in EXTRA_DIST.

You can also mention a directory in EXTRA_DIST; in this case the entire directory will be recursively copied into the distribution. Please note that this will also copy everything in the directory, including CVS/RCS version control files. We recommend against using this feature.

If you define SUBDIRS, Automake will recursively include the subdirectories in the distribution. If SUBDIRS is defined conditionally (see Conditionals), Automake will normally include all directories that could possibly appear in SUBDIRS in the distribution. If you need to specify the set of directories conditionally, you can set the variable DIST_SUBDIRS to the exact list of subdirectories to include in the distribution (see Top level).

Should we, therefore:

get rid of the "doc/" entries in the EXTRA_DIST in the top-level Makefile.am, and make sure the one in "doc" causes all the files listed therein to be included in the distribution;

make sure tools/Makefile.am causes all the stuff under "tools" to be included in the distribution?