Removing .mo files from cvs
I'm strongly considering removing .mo files from cvs and the tar.gz file, possibly for Mailman 2.1.2.
The files can easily be created at build time, even if gettext doesn't exist. We have a pure-Python version of msgfmt
It cuts out about 4MB uncompressed from the tar file
Having .mos makes creating patches more difficult.
It should greatly speed up cvs update.
I'd like to know if anybody has objections to this. It would actually make the translation teams job easier since you won't have to worry about building or checking in the .mo files.
I have this working in an unchecked in snapshot. Before I commit it I wanted to see if anybody has major objections or can see any flaws.
-Barry
On Mon, Apr 21, 2003 at 02:17:26PM -0400, Barry Warsaw wrote:
I'm strongly considering removing .mo files from cvs and the tar.gz file, possibly for Mailman 2.1.2.
From CVS, it's a Good Thing. I'm not sure about tar.gz's.
- The files can easily be created at build time, even if gettext doesn't exist. We have a pure-Python version of msgfmt
Is this msgfmt.py distributed in the tarball? If yes, I guess it's ok. If no, I'd leave them in. If they are removed, they should probably be built by the normal "make all" rule without needing external tools (automake-made tarballs are like this).
Jordi
Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jordi@sindominio.net jordi@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/~jordi/
On Mon, 2003-04-21 at 14:24, Jordi Mallach wrote:
On Mon, Apr 21, 2003 at 02:17:26PM -0400, Barry Warsaw wrote:
I'm strongly considering removing .mo files from cvs and the tar.gz file, possibly for Mailman 2.1.2.
From CVS, it's a Good Thing. I'm not sure about tar.gz's.
- The files can easily be created at build time, even if gettext doesn't exist. We have a pure-Python version of msgfmt
Is this msgfmt.py distributed in the tarball?
It would be. It comes verbatim from Python's Tools/i18n/msgfmt.py.
If yes, I guess it's ok. If no, I'd leave them in. If they are removed, they should probably be built by the normal "make all" rule without needing external tools (automake-made tarballs are like this).
They would definitely be built with "make all".
Thanks for the feedback. -Barry
lunedì, 21 aprile 2003 alle 14:17:26, Barry Warsaw ha scritto:
I'm strongly considering removing .mo files from cvs and the tar.gz file, possibly for Mailman 2.1.2. [...] I have this working in an unchecked in snapshot. Before I commit it I wanted to see if anybody has major objections or can see any flaws.
+1
-- This signature intentionally left blank
participants (3)
-
Barry Warsaw -
Jordi Mallach -
Simone Piunno