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

[Bruno Haible]

Hello,

> 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.

That's OK, because the native /usr/lib/libintl* has not all the functionality
of the GNU libintl.

> But gettext-tools under NetBSD installs same files with same conflicting
> names.

Since gettext-tools depends on gettext-runtime, the easiest thing for
you to do is to manually remove them from the installation file list.
Or, if you don't have an explicit file list, just "rm" them after
gettext-tools' "make install", but before the packaging step. You can
do so faithfully, because the gettext-tools package actually compiles
it from the gettext-runtime source.

> (Under Linux, it installs libgnuintl* which wouldn't conflict.)

How come?! libgnuintl* should not be installed on *any* system. It is
a private build, meant for the testsuite only.

> Also, I wonder if maybe the gettext-runtime should install the libgnuintl*
> versions always.

No no no, libgnuintl* should never be installed!

Thanks for asking; so many other packagers publish binary packages that are
broken in one or the other way. (For example, the idea of an gettext-m4
package is nonsense because the gettextize _program_ uses the m4 macros.)

Bruno