Use gcov to find how much code coverage our current testing gets. This
can be enabled by passing --with-gcov to configure and running "make
gcov". This is limited to gcc. Here's a run from the current code (for
some reason, gcov insists on profiling gstring.h).
/usr/bin/gcov pkg.h pkg.c parse.h parse.c main.c
File 'pkg.c'
Lines executed:73.16% of 611
pkg.c:creating 'pkg.c.gcov'
File '/usr/include/glib-2.0/glib/gstring.h'
Lines executed:100.00% of 6
/usr/include/glib-2.0/glib/gstring.h:creating 'gstring.h.gcov'
File 'parse.c'
Lines executed:79.67% of 492
parse.c:creating 'parse.c.gcov'
File 'main.c'
Lines executed:57.34% of 293
main.c:creating 'main.c.gcov'
When reapplying the glib patches we often end up with .orig files when
the hunks have moved. Any backup suffix is possible, but this is the
default from patch(1).
We want to use the libtool script to determine if indirect dependencies
should be listed. LT_OUTPUT forces the script to be created immediately
so that the test can be run reliably.
This is borrowed from glib's configure.in.
In order to avoid having the COPYING file from automake included in
the distribution, add a copy of the GPLv2 for pkg-config. This matches
the source files, which all specify GPLv2+.
The COPYING file from upstream popt has also been added for the
bundled popt sources.
