[pkg-fetchmail-maint] FYI: regarding .gmo files

[Héctor García]

El lun, 09-01-2006 a las 12:18 +0100, Matthias Andree escribió:
> Greetings,
> 
> after the discussion between Nico and Héctor, I've today tried to port
> .gmo files that I built on Linux-i386 (little endian) to Solaris 8-SPARC
> (big endian) - no problem.
> 
> There should be no reason to rebuild .gmo files as part of the
> installation. After all, GNU gettext invented this format to overcome
> problems with system-specific .mo formats. I believe the documentation
> inside gettext that mentions .mo were non-portable refers to the non-GNU
> .mo formats.

There is another problem. 
If I update any .po file, and include my update as a patch until the
update is released by a new upstream version, package building in debian
will fail if I call update-gmo and the .gmo file existed on the
orig.tar.gz file.
To avoid this (missing updates on .po files and/or breakage of package
build) the best solution is to not include the .gmo as part of upstream
release but create them on build time.
I don't know your reasons to release the .gmo files but is not the usual
thing to do. The release of binary files that can (and really should) be
build from the sources has no much sense.

Regards,

Héctor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-fetchmail-maint/attachments/20060109/1a69294c/attachment.pgp