Re: Intltool and disting of .gmo files

[Rodney Dawes <dobey novell com>]

On Tue, 2005-03-01 at 11:02 +0800, James Henstridge wrote:
> Rodney Dawes wrote:
> 
> >Currently, intltool is distributing the generated .gmo files, within
> >tarballs. Christian Persch recently filed a bug against intltool, as
> >this still causes some issues with builddir != srcdir. I'd prefer to
> >not duplicate generated files if possible. If anyone has sufficient
> >reason as to why they should be distributed, please speak up now, or
> >I'm going to fix intltool to stop distributing them tonight, and make
> >a release with some other fixes as well. The bug in question is:
> >
> >http://bugzilla.gnome.org/show_bug.cgi?id=166724
> >  
> >
> I think the reason why gettext's Makefile.in.in distributes the .gmo 
> files is so that you can install the translations from a tarball install 
> even if you don't have the gettext utilities installed (msgfmt, etc).

Perhaps. I think it's safe to assume that if one doesn't have gettext
installed though, they probably don't want translations anyway, if they
are building from source. Translators should really have the gettext
tools installed anyway, so that they can test their changes.

> I haven't noticed any builddir!=srcdir problems with the stock gettext 
> or glib-gettextize Makefile.in.in, so I guess this is an intltool 
> specific problem.  Is there any reason not to follow what the existing 
> tools do here?

I'm surprised glib-gettextize's Makefile.in.in would work. Intltool's
Makefile.in.in is almost exactly the same as glib's, with appropriate
changes to use intltool's maintanence utilities and the like. Though, it
does look like the glib-gettextize Makefile.in.in likes to generate the
gmo files and pot file in srcdir instead of builddir. That seems more
broken to me.

Anyway, favortism seems to support not disting the gmo files, as it
saves quite a bit of size in the tarball, so I'm going to commit the
change.

-- dobey