From: Didier Verna <didier@lrde.epita.fr>
Cc: ding@gnus.org
Subject: Re: ./configure
Date: Mon, 30 Jul 2001 10:19:48 +0200 [thread overview]
Message-ID: <muxr8uyakwr.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <y68puavk57n.fsf@hodge-podge.mit.edu> ("David Z. Maze"'s message of "Fri, 20 Jul 2001 11:09:16 -0400")
"David Z. Maze" <dmaze@MIT.EDU> wrote:
> Mattias Ahnberg <mattias@ahnberg.pp.se> writes:
>Ahn> I just[1] downloaded gnus via CVS, got all files nicely enough and
>Ahn> started looking around a little. What struck me strange is that I
>Ahn> didn't get a "configure" file with it, something changed recently
>Ahn> that I missed, or is something wrong?
>
> That's pretty typical for stuff in CVS; you don't actually want to
> store the configure script proper, because it's generated from
> configure.in and depends on basically nothing beyond that file and the
> version of autoconf you're using. You can generate configure from
> configure.in by running 'autoconf'.
Well, you actually *want* to keep configure in CVS because it is no
different from people to people, and it's somewhat insane to make thousands of
people regenerate the *same* file. It also has the advantage that CVS simple
users (not developers) don't have to know autoconf and friends to build gnus.
"What goes in a distro goes to CVS" -- I can't remember who said that :-)
--
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 44 08 01 99 didier@xemacs.org
next prev parent reply other threads:[~2001-07-30 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 20:59 ./configure Mattias Ahnberg
2001-07-20 15:09 ` ./configure David Z. Maze
2001-07-20 17:54 ` ./configure ShengHuo ZHU
2001-07-30 8:19 ` Didier Verna [this message]
2001-07-30 14:32 ` ./configure Stainless Steel Rat
2001-07-30 18:09 ` ./configure ShengHuo ZHU
2001-07-30 23:58 ` ./configure Karl Eichwalder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=muxr8uyakwr.fsf@uzeb.lrde.epita.fr \
--to=didier@lrde.epita.fr \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).