Subject: Re: pkg/21040 (libintl management in packages)
To: None <,,>
From: Quentin Garnier <>
List: pkgsrc-bugs
Date: 10/02/2006 21:40:02
The following reply was made to PR pkg/21040; it has been noted by GNATS.

From: Quentin Garnier <>
Subject: Re: pkg/21040 (libintl management in packages)
Date: Mon, 2 Oct 2006 23:37:45 +0200

 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 On Mon, Oct 02, 2006 at 07:45:02PM +0000, Joerg Sonnenberger wrote:
 > The following reply was made to PR pkg/21040; it has been noted by GNATS.
 > From: Joerg Sonnenberger <>
 > To:
 > Cc:=20
 > Subject: Re: pkg/21040 (libintl management in packages)
 > Date: Mon, 02 Oct 2006 21:38:48 +0200
 >  On Mon, Oct 02, 2006 at 07:25:02PM +0000, Quentin Garnier wrote:
 >  >  > Feedback expired. Also (with the gettext maintainer head)
 >  >  > consider this bug as fixed by proper use of PREFER_PKGSRC.
 >  > =20
 >  >  This is BS.  The PR is about packages having requirements that
 >  >  are met differently by the system.  The user, and therefore
 >  >  PREFER_PKGSRC, is not involve.  Sure, PREFER_PKGSRC would fix it, but
 >  >  how can the user know the problem exists beforehand?
 > =20
 >  The interface of system gettext and pkgsrc gettext is the same, so this
 >  is about choosing one implementation over the other. Mixing them doesn't
 >  work and the mechanism for choosing one of the other in pkgsrc is *tata*
 > =20
 >  The reason why that doesn't work is simply that the set of symbols
 >  providing by pkgsrc gettext is prefixed with libintl, the native version
 >  doesn't have prefixes.
 > =20
 >  There are other limitations like missing support for pluralisation in
 >  older NetBSD releases and those are worked around by pkgsrc. It is the
 >  responsibility of the user to decide what he needs (if he hits the few
 >  issues) and whether it is worth the pain.
 Could you please at least read the contents of the PR?  In that case it
 was the issue of gettext not being able to parse UTF-8 locales.  AFAICT,
 pkgsrc doesn't work around that issue.  And there is no way for the user
 to know about the issue until a number of packages are already built,
 which is even more of a pain.
 Sure, as soon as NetBSD 2.0 is EOL'd you'll be able to close the PR, but
 in no way it will have been addressed.
 Quentin Garnier - -
 "You could have made it, spitting out benchmarks
 Owe it to yourself not to fail"
 Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: GnuPG v1.4.3 (NetBSD)