From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: ./configure
Date: Mon, 30 Jul 2001 10:32:51 -0400 [thread overview]
Message-ID: <01Jul30.103401edt.115238@gateway.intersys.com> (raw)
In-Reply-To: <muxr8uyakwr.fsf@uzeb.lrde.epita.fr>
* Didier Verna <didier@lrde.epita.fr> on Mon, 30 Jul 2001
| 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.
"CVS versions" and "simple user" do not go together. If you are using
something out of a CVS tree then you are either a) an advanced user, b) a
developer, or c) a tester, all three of which should have at least a basic
understanding of how automake work. If you are none of the above then you
probably should not be using anything out of a CVS tree.
Besides "./autogen.sh" is not that difficult, and it runs configure for you
automatically. That is how most of the projects that I use out of CVS
trees handle things. The only one I don't is Mozilla, which has its own
config mechanism.
--
Rat <ratinox@peorth.gweep.net> \ If Happy Fun Ball begins to smoke, get
Minion of Nathan - Nathan says Hi! \ away immediately. Seek shelter and cover
PGP Key: at a key server near you! \ head.
next prev parent reply other threads:[~2001-07-30 14:32 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 ` ./configure Didier Verna
2001-07-30 14:32 ` Stainless Steel Rat [this message]
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=01Jul30.103401edt.115238@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).