[Pkg-gnutls-maint] libgcrypt11

Andreas Metzler ametzler at downhill.at.eu.org
Mon Jun 19 18:09:22 UTC 2006


On 2006-06-18 James Westby <jw+debian at jameswestby.net> wrote:
[...]
> What does this mean for the package? The lines from debian/control are 

> Build-Depends: debhelper (>> 4.1.0), docbook-utils, tetex-bin,
> docbook-to-man, jade, texinfo (>= 4.6-1), cdbs, texi2html (>= 1.76-1),
> libgpg-error-dev, binutils, autotools-dev

> Build-Depends-Indep: debhelper (>> 4.1.0), docbook-utils, tetex-bin,
> docbook-to-man, jade, texinfo (>= 4.6-1), cdbs, texi2html

> So, Build-Depends contains all of the packages of B-D-I, but with a
> stronger restriction on texi2html. 

> My reading of this is that the B-D-I field can just be dropped from the
> package, as it doesn't specify any extra packages, or a more restrictive
> set. Have I got this correct? 

Yes.

> As for the rest of the packaging I cannot understand most off the
> diff.gz from the last version, it seems to make lots of changes to the
> source, many of which I cannot see the point of. For instance it
> includes whole files that were removed upstream a couple of years ago.

Afaik Matthias synced upstream's CVS (or SVN) repositories into
private git repositories http://netz.smurf.noris.de/cgi/gitweb?o=age
somehow this syncing seems to have missed most of the file deletions.
As the packages where built from the repository also all autogenerated
files (autof*,  *.ps, *pdf, ...) will also differ. (See also #367358).

So for extracting the interesting stuff we will be able to
a) probably ignore any file additions, except caused by c
b) ignore any auto* files

however 
c) we will need to find out first whether the 1.2.2-1 package contains
upstream's 1.2.2 or some later changes. There cannot be many as the
package appeared shortly after (Tue, 18 Oct 2005) 1.2.2's release (Oct
5).

> The current svn version leaves out most of the changes, and seem to
> build the same, but I'm not positive. 

> In the other packages you have used --enable-ld-version-script instead
> of hacking configure.in, what are the hacks that were being used? I'm
> not sure if those are the changes that are seen here. 

The other packages changed configure.in to check for the GNU linker
and use versioned symbols if they are found, if this is not case,
libtool's -export-symbols-regex switch was used to at least not export
everything. Upstream's version is worse imho:
if arch is *linux* or *gnu* or --enable-ld-version-script was used use
versioned symbols otherwise do nothing.

cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde



More information about the Pkg-gnutls-maint mailing list