Subject: Re: gnupg2 build failure on netbsd-3
To: None <tech-pkg@NetBSD.org>
From: Greg Troxel <email@example.com>
Date: 12/11/2006 08:24:40
Joerg Sonnenberger <firstname.lastname@example.org> writes:
> On Mon, Dec 11, 2006 at 08:00:19AM -0500, Greg Troxel wrote:
>> The other issue is that expressing that one needs 0.14.1 in the
>> Makefile should cause devel/gettext-lib/buildlink3.mk to pull that in,
>> or there should be some way to tell USE_TOOLS that one needs a newer
>> version. I'm a bit perplexed as to USE_TOOLS vs. the bl3; it seems
>> USE_TOOLS is for build time and bl3 for linking. It seems to be
>> asking for trouble to use newer tools and an older library, though.
> The file format doesn't change. Cherry picking gettext is asked for
> trouble, just as cherry picking iconv is often difficult to dangerous.
> I don't think there's any proper reason to require linking with another
> gettext version and at least the gettext in NetBSD 4 will be good enough
> for this I think.
gnupg2 currently fails to build on NetBSD 3. It's fine in current and
has been fine for a while, so I'm sure it's ok in netbsd-4.
I agree that cherrypicking (by which I mean taking part of a gettext
release and no the whole thing) is dangerous. Assuming the file
format hasn't changed is also dangerous (even if it's correct), or at
least not well documented in the pkgsrc build system why such
optimizations are safe.
The current problem is that it isn't possible to express in pkgsrc
that one needs a specific version; there's a built-in notion of "good
enough" which in this case isn't a high enough version for an upstream
package's documented requirement.
Greg Troxel <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)
-----END PGP SIGNATURE-----