[Bug-gnubg] 0.14.3 packages uploaded to Debian unstable

[Russ Allbery]

I've finished building and testing 0.14.3 packages and have uploaded them
to Debian unstable.  The new packages are built with as many of the
options and prerequisites as are available in Debian, so should be fairly
thorough.  There are three packages, gnubg, gnubg-data, and
gnubg-bearoffs; the last contains the bearoff databases and is optional to
install.

In addition to the gcc 4 patch, the man pages, and the GFDL issue that I
sent messages about separately, the Debian package has the following
modifications:

 * The configure script has been modified to pick up the dynamic Python
   libraries instead of the static ones.  The patch is a little specific
   to Debian in that it assumes the Python libraries are available in the
   normal linker search path; that probably won't be the case everywhere.

 * The ISO 8859-1 characters in the man page were replaced with groff
   escapes, which aren't dependent on the assumed local character set.
   This probably isn't suitable for the general distribution since one
   unfortunately can't assume every system uses groff for man pages.

 * I hacked up the Makefile a little to link gnubg only with those
   libraries it uses directly, rather than also linking it with all the
   libraries those libraries depend on.  This is for Debian packaging
   reasons to reduce the number of direct dependencies of the package,
   which makes later library transitions much easier.  This is a rather
   ugly change, unfortunately, that I'll probably have to maintain
   separately in the Debian package.  There isn't any good way to do this
   generally without extensive modifications to the build process.

The new packages are currently waiting for Debian ftp-master approval
since I split the architecture-independent data files into a separate
package, but will likely show up in a few days.

It occurred to me that there's no need to package the bearoff database;
instead, gnubg could just optionally generate the bearoff database when
the package is installed based on the user response to a debconf prompt.
That should be a fairly straightforward change and will save some archive
space.  After this version gets into the archive and I can check whether
it has any build problems on all the architectures Debian supports, I'll
probably make that change.

-- 
Russ Allbery (address@hidden)             <http://www.eyrie.org/~eagle/>