On Tue, Jun 3, 2014, at 13:27, Karel Zak wrote: > On Mon, Jun 02, 2014 at 12:33:23PM +0200, Ruediger Meier wrote: > > 1. Don't track these po files in git at all. Always generate in > > builddir. Put them into dist only. > > No, I'm sure we want to have .po files in the git, it's part of the package. Well, I think it's nice to have copies of those files in many repos around the globe, but it's not really needed. And thus several GNU packages (coreutils, grep, tar) have chosen to drop the PO files from their version control. The files get fetched from the TP at release time. > > 2. Don't update them with "make dist". Add new target "make update-po". > > Well, I use "make distcheck" to generate the final release tarballs > and it would be nice to keep it usable :-) Easy: add another target, "make release", that does an update-po and then distcheck. :) Benno -- http://www.fastmail.fm - Send your email first class -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
