On Wed, Jun 06, 2012 at 12:28:02PM +0200, Hilko Bengen wrote:
* Richard W.M. Jones:
> Since these (*.gmo) files are built, shouldn't they in fact be in
> builddir?
But they are shipped with the tarballs. So, shouldn't they be built in
$(builddir)?
I think you mean "shouldn't they be built in $(srcdir)?". Yes, that
could be correct, unless we rely on people having 'msgfmt' installed.
> The *.po files are generated during the build, but are really
source
> files because (a) they go in the tarball and (b) they are modified by
> translators and the changes that the translators make are '.PRECIOUS'.
Do you mean that the commands to rebuild the .po files always operate in
$(srcdir)?
Hopefully :-)
The *.po files are an odd case. In reality they are managed by
Transifex, so they can always be downloaded from there (using "tx
pull" or preferably the "./tx-pull.sh" wrapper in the toplevel
directory). However since pulling them is slow, people aren't
expected to have the tx tools installed, and (most importantly)
because Transifex prevents anonymous pulls, we bundle them in git and
the tarball as if they were source files.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top