On Tue, Sep 01, 2015 at 06:28:28PM +0200, Jérémy Bobbio wrote:
> Santiago Vila:
> > Excluding .pot files from what is considered to be the "source" might
> > be part of the problem.
> See tor-monitor upstream's reaction, for example:
> https://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/Week-of-Mon-20150824/000015.html
> Quoting Alan from there:
> > I didn't add the .pot in git because it's generated at build time.
> > Adding it duplicates info and adds the risk that it's not up-to-date.

Well, upstream authors using autoconf in their projects usually don't
put the autogenerated "configure" script in the git repository
(which I understand), but they include it in the release tarball.

I think .pot files belong to the same class of files that belong to
release tarballs, i.e. the kind of files that (normally) should not be
created at build time because they are already there.

> I'd be happy to hear more arguments for/against.

Yes, so would I.

Maybe I should ask the author.

Reproducible-builds mailing list

Reply via email to