Re: configure scripts in mercurial

> Here and now is the right time and place for people to voice their
> opinions - do you like the current system (configure scripts in
> mercurial) or would you prefer the Emacs style (configure scripts in the
> distribution tar ball but regenerated by each developer).

I believe that the best way is to have a simple ./configure script
which is _not_ generated, but written by hand. Such a script is
then in the repository of course. For example http://mdocml.bsd.lv/
does this precisely to avoid dealing with the various versions of auto*.
(It also avoids this question.)
http://mdocml.bsd.lv/cgi-bin/cvsweb/configure

If the ./configure is to be regenerated from configure.in,
then a generated ./configure should be present in every
distribution tarball of course, but not in the repo,
being a generated file.

> > Somehow, it would be a pain for a user to have to get clisp source
> > from hg but a working configure from inside a downloaded distribution,
> > instead of having everything in the tree.
> 
> This is not right. You should regenerate the configure files yourself.

Yes.

	Jan


------------------------------------------------------------------------------
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel