[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-tracker] [bug #25194] Duplicity 5.04 Requires python-distutil

From: Michael Terry
Subject: [Duplicity-tracker] [bug #25194] Duplicity 5.04 Requires python-distutils-extra package plus intltool and others
Date: Mon, 29 Dec 2008 16:56:11 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5

Follow-up Comment #4, bug #25194 (project duplicity):

OK, my bad.  It wasn't showing up on a cvs update (is there a different
command to use to get new dirs?), but a fresh checkout showed it.

Makevars has a couple lines with your email address that apparently should be
quoted, as apparently some toolchain versions don't handle the spaces well (as
reported on the mailing list).  My fault.

Speaking of toolchains, how does one generate the .pot file and work with new
po files?

Before, the po directory in the tar contained Makevars and POTFILES.in, and
when it was built, it would create the .pot file.  A translator could run
'msginit -l fr' to create a new French translation based on that pot file.  I
think the makedist script should ship Makevars, POTFILES.in, duplicity.pot
(generated at makedist time), and any po files in the CVS 'po' directory. 
Most translation services expect all that in the source tarball and have tools
that process them accordingly.  And it's a bonus kindness to them if the pot
file is in there already.

You asked for some documentation on how the whole translation flow works, and
I'll try to get that to you.

If we wanted to continue down the path of requring translators to work in
CVS, you'd need to modify POTFILES.in to point at the CVS locations
(duplicity/*.py instead of src/*.py).  But I wouldn't recommend it.

Lastly, dist/setup.py seems to have been committed with the "test" version
instead of "$version".


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]