Ubuntu
pkgbinarymangler package

  1. Bug #978724
  2. Comment #7

Comment 7 for bug 978724

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 978724] Re: pkgbinarymangler should build a tarball for pot import even when translations are not stripped

Steve Langasek [2013-05-17 14:45 -0000]:
> Regenerating the .pot file at package build time changes timestamps,
> which means the .mo files shipped in the package are not identical
> across architectures.

I don't understand this. This would only happen if the package updates
its *.po files during package build, which is evil and unnecessary.
But build systems which do that would already create different *.mo
files on each build, so whether or not you update the *.pot as well
should make little difference.

In the ordinary case, the build sytem just builds *.mo from the source
*.po files, and completely ignores the *.pot. Most binary packages get
their *.mo files stripped out anyway, and for the remaining ones we
just need to make sure that we don't put *.mo files into arch specific
packages (either packages are arch:all anyway, or we put translations
into an arch:all -common binary, which is quite common for GNOME
packages).