packaging gettext-runtime-0.14.1 and gettext-tools under NetBSD

[Jeremy C. Reed]

Hello,

I am working on gettext-runtime-0.14.1 and gettext-tools-0.14.1 packages
for the portable pkgsrc[1] packaging build system.

I am building as suggested in the PACKAGING file

(Plus I configured with --mandir=${PREFIX}/man for both so it wouldn't go
into default prefix/share/man.)

Under Linux, the packages build and install fine. But under NetBSD 1.6.2,
I have file conflicts between the two.

Under NetBSD, the gettext-runtime installs (in addition to other files):

 include/libintl.h
 lib/charset.alias
 lib/libintl.a
 lib/libintl.la
 lib/libintl.so
 lib/libintl.so.7
 lib/libintl.so.7.0
 ${PKGLOCALEDIR}/locale/locale.alias

which is fine even though a native /usr/lib/libintl* is available. (It
installes to /usr/pkg/ by default so is okay.)

But gettext-tools under NetBSD installs same files with same conflicting
names. (Under Linux, it installs libgnuintl* which wouldn't conflict.)

So under NetBSD, I do not want gettext-tools to install duplicates since
it requires (according to PACKAGING) gettext-runtime anyways.

Any suggestions before I start hacking this code?

Also, I wonder if maybe the gettext-runtime should install the libgnuintl*
versions always. And if not Linux, then also create symlinks (for
libintl)?

And then with gettext-tools package do not install any libgnuintl (nor
libintl) files.

Any advice would be appreciated.

Please carbon-copy on all replies.

Thank you,

   Jeremy C. Reed
   http://bsd.reedmedia.net/

[1] pkgsrc already has gettext, gettext-lib and gettext-m4 packages, but
they are based on old 0.11.5 code. pkgsrc is a portable package building
system that provides: 1) a categorized collection of specifications for
fetching, checking checksums, patching, configuring, building, installing
and packaging software suites; 2) package installation and maintenance
tools. pkgsrc is used under Linux, NetBSD, Darwin, Mac OS X, Irix,
SunOS/Solaris, AIX, HPUX, BSD/OS, FreeBSD, Windows and other operating
systems for managing nearly 5000 software suites.