On 2010/11/4 Colin Watson wrote: [...] > The next thing in the build sequence would be debian/build/man. > > <cjwat...@sarantium ~/src/debian/man-db/trunk/man-db>$ svn st > M debian > M debian/changelog > M debian/rules > <cjwat...@sarantium ~/src/debian/man-db/trunk/man-db>$ make -C > debian/build/man/po4a > make: Entering directory > `/home/cjwatson/src/debian/man-db/trunk/man-db/debian/build/man/po4a' > make[1]: Entering directory > `/home/cjwatson/src/debian/man-db/trunk/man-db/debian/build' > make[1]: Leaving directory > `/home/cjwatson/src/debian/man-db/trunk/man-db/debian/build' > po4a --variable srcdir=../../../../man --variable builddir=../../man --keep > 0 ../../../../man/po4a/po4a.cfg > make: Leaving directory > `/home/cjwatson/src/debian/man-db/trunk/man-db/debian/build/man/po4a'
Thanks for this detailed bug report. Please note that technically this is not an out-of-tree build, your command works like gcc -I../../src -o ../../src/foo.o ../../src/foo.c To me, an out-of-tree build would be po4a --srcdir ../../../../man ../../../../man/po4a/po4a.cfg with po4a.cfg containing [po4a_langs] id pl ru [po4a_paths] po4a/po/man-db-manpages.pot $lang:po4a/po/$lang.po [po4a_alias:man] man opt:"-L UTF-8 -o groff_code=verbatim" [type:man] man1/apropos.man1 $lang:$lang/man1/apropos.man1 add_$lang:$lang/translator.add [type:man] man1/lexgrog.man1 $lang:$lang/man1/lexgrog.man1 add_$lang:$lang/translator.add [type:man] man1/man.man1 $lang:$lang/man1/man.man1 add_$lang:$lang/translator.add [type:man] man1/manconv.man1 $lang:$lang/man1/manconv.man1 add_$lang:$lang/translator.add [type:man] man1/manpath.man1 $lang:$lang/man1/manpath.man1 add_$lang:$lang/translator.add [type:man] man1/whatis.man1 $lang:$lang/man1/whatis.man1 add_$lang:$lang/translator.add [type:man] man1/zsoelim.man1 $lang:$lang/man1/zsoelim.man1 add_$lang:$lang/translator.add [type:man] man5/manpath.man5 $lang:$lang/man5/manpath.man5 add_$lang:$lang/translator.add [type:man] man8/accessdb.man8 $lang:$lang/man8/accessdb.man8 add_$lang:$lang/translator.add [type:man] man8/catman.man8 $lang:$lang/man8/catman.man8 add_$lang:$lang/translator.add [type:man] man8/mandb.man8 $lang:$lang/man8/mandb.man8 add_$lang:$lang/translator.add Unfortunately, an error is reported with po4a 0.40.1, this one is already fixed in our SVN repository. Next, this command may update POT and PO files (this depends on timestamps), which is the point of this bugreport. > <cjwat...@sarantium ~/src/debian/man-db/trunk/man-db>$ svn st > M debian > M debian/changelog > M debian/rules > M man/po4a/po/ru.po > M man/po4a/po/pl.po > M man/po4a/po/id.po > > It would be very helpful if there were a way to force this not to > happen. When I'm doing out-of-tree builds, I certainly do not want PO > and POT files to be updated. In fact, in general I would prefer to be > able to cause the 'make' step never to update PO and POT files, only > 'make dist' or similar. Oh, this statement reminds me that I forgot to state my opinion about that in the other bug report. The 'make dist' target had been invented long before VCS were in common usage, tarballs were the most common way to publish sources. My interpretation is that gettext maintainers wanted to make sure that distributed PO files where up-to-date, that is why 'make dist' rebuilds them. But nowadays the situation is very different, translators have access to PO files at any time. If they were designing gettext now, IMHO they could let 'make' update PO files. I have to think more about your problem. > I could use --translate-only, but that seems rather more tedious to use. Right, this option has been introduced to solve a very different problem: manpages contains hundreds of files, and a l10n team did not want to rebuild all manual pages to check their changes. With this option, they can run po4a --translate-only man3/foo.3 man3/man3.cfg Denis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
