Re: libfoo2 vs. libfoo
- From: Maciej Stachowiak <mjs noisehavoc org>
- To: jacob berkman <jacob ximian com>
- Cc: gnome-2-0 <gnome-2-0-list gnome org>
- Subject: Re: libfoo2 vs. libfoo
- Date: Mon, 15 Oct 2001 11:32:22 -0700
On 15Oct2001 02:37PM (-0400), jacob berkman wrote:
> hello,
>
> so there's no good reason to name the various tarballs "libfoo2". gtk+
> has a special po/Makefile.in.in which uses GETTEXT_PACKAGE to get around
> the translations conflicts.
>
> this affects libgnome*, gnome-vfs, gconf, libbonobo*, etc.
>
> are there any problems with going this route?
Is there any way to do this without checking in a modified
po/Makefile.in.in? Some autogen.sh scripts run gettextize and will
overwrite this file. It also doesn't seem very robust against gettext
version changes.
For intltool (the module formerly known as xml-i18n-tools) we patch
the po/Makefile.in.in after it gets copied in. In this case a cleverly
chosen sed job might do the trick (since the patch would have to be
aoutomatically generated.
- Maciej
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]