On 2014-10-20 Nick Bowler <nbow...@elliptictech.com> wrote: > > Not exactly. Distcheck first creates a distribution tarball (i.e., > make dist), THEN it unpacks the tarball into a temporary srcdir and > tests that. In other words, distcheck is directly testing the 'user > experience' when they unpack a tarball you publish. > > Part of that user experience is that the following sequence should work: > > - download your package tarball from a website. > - unpack it > - ./configure && make dist > > Since your script is not distributed, that sequence must not require the > script to work.
Thanks! Now I understand how distcheck really works. I'll just make the ChangeLog target check if the script and .git are available, as you suggest. Problem solved :-)
signature.asc
Description: PGP signature
