From: Rafael Laboissiere <laboissiere@ps...> - 2003-03-07 08:34:39
* Alan W. Irwin <irwin@...> [2003-03-06 11:06]:
> A practical question. How do we do this for ourselves? make won't work
> until you configure.
This is the recipe:
cvs co plplot
./configure --enable-docbook --enable-python
Of course, for that to work you must have the Docbook tools, the latest Swig
and the appropriate version of the Autotools. The recipe above should
produce the same tarball as mine, apart the version number. I apply a little
trick to change the version string based on the current date. The gory
details are in scripts/make-cvs-tarball.sh.
> Is the tarball result completely independent of what the configuration
> options are? For example, if you disable all drivers except null and
> disable all front ends do you still get the same tarball result? Also, what
> happens if you do/don't enable the documentation building?
There are two issues here. First, the resulting tarball should contain at
least all the files that are in CVS (except the evident exclusions like
new/, tmp/, and friends) regardless of the configure options. This is a
matter of having the EXTRA_DIST variables (and others associated with them)
declared outside the Automake conditionals. This is not the case at
present. I tried to fix some cases, but there are some old style stuff in
some of the Makefile.am's. I will try to sort out the problems.
The second issue is about the things that are built to be included in the
tarball, like the printable, html, info, and man forms of documentation and
the Swig related stuff (for now, I just tried Python, not Java). I am not
yet sure that my logic in the relevant Makefile.am's is fully correct.
At any rate, the recipe above should work for now.
> Excellent news. And I second your thanks to David for keeping this going
> while you were otherwise engaged. That is a long and impressive list of
> Debian bug reports that this release addresses, [...]
Actually, David _fixed_ a lot of those reported bugs. I just _closed_ them
with the upload because only the official maintainer can close bugs through
the dinstall (Debian installer) interface.
> [...] and I expect the additional bug reports from the Debian community on
> your new packages will be a great benefit to PLplot as a whole. Also, for
> this same reason I hope your packages will shortly migrate to testing where
> there are many more Debian users/testers.
There is a another Debian developer who is currently backporting my packages
to woody. More on that later, keep tuned.