[Ur] Best practices for Mercurial + autogeneration of files?

[Jason Gross]

Do you know about/have you considered using `make dist` (
http://www.gnu.org/software/automake/manual/automake.html#Basics-of-Distribution)?
 It does not currently work, failing with "cp: cannot create regular file
`urweb-20120925 + c8ecea593347 tip/m4/ax_check_openssl.m4': No such file or
directory".  However, when it works, it automatically includes a number of
common autogenerated files, including "configure".

-Jason

On Wednesday, July 17, 2013, Adam Chlipala wrote:

> A few people have suggested changing the Ur/Web repository so that
> autogenerated files like 'configure' are not included.  There's a Mantis
> issue here:
>     http://www.impredicative.com/**mantis/view.php?id=158<http://www.impredicative.com/mantis/view.php?id=158>
>
> Here's my question, which is about an issue not addressed directly in the
> text of that "bug report": What would be the best way to package a version
> control snapshot as a source distribution?  Right now, I use the 'hg
> archive' command, which builds a tarball directly from the repository.
>  There is no need to worry about accidentally including generated files
> that should not be distributed.  Would it be necessary to get much fancier,
> with a 'tar' filename blacklist or whitelist, if I want to distribute a
> generated 'configure' file along with other sources drawn directly from the
> repo?
>
> ______________________________**_________________
> Ur mailing list
> Ur at impredicative.com
> http://www.impredicative.com/**cgi-bin/mailman/listinfo/ur<http://www.impredicative.com/cgi-bin/mailman/listinfo/ur>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.impredicative.com/pipermail/ur/attachments/20130805/5b32e712/attachment.html>