On Wed, Jan 04, 2006 at 06:30:23PM +0100, Christian Stimming wrote: > Chris Shoemaker schrieb: > >On Wed, Jan 04, 2006 at 11:23:01AM +0100, Christian Stimming wrote: > > > >>Neil Williams schrieb: > >> > >>>>Does anyone know why we version-control this generated file? > >> > >>No, please don't remove it. The reason why we version-control this > >>generated file is because the Makefile in that directory is not under > >>our control (but instead gettext's) and it doesn't contain any rules for > >>creating that file. The gettext setup assumes by convention that this > >>file exists and doesn't need to be generated, so as long as we use the > >>gettext build system in the po directory, we need to follow that > >>convention. > > > >I thought there was some reason, I just couldn't remember. Instead of > >reverting, I'll commit a stub po/POTFILES.in explaining why the file > >is in SVN. Then maybe we can set an ignore property for it. > > Err, what does a stub help here? The point is that people (and maybe > translators) run "make" and expect that the gnucash.pot will be > correctly built. This is only achieved if there is a ready-to-use > po/POTFILES.in in SVN, IMHO. This is what gettextize conventions are, so > we have to stick to that. I don't understand how else you try to achieve > this.
The goal is just to make it so we're not breaking the build or leaving out files if we add/delete/rename files and forget to update POTFILES.in. Any suggestions? -chris _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
