Vin Shelton <acs(a)alumni.princeton.edu> writes:
Didier wrote:
> What ?! Could you explain why ?
I've always advocated a model where configure only does what I tell it to.
Take a random package using a `configure' script. Build it and
`make install' it. Well, without /telling/ it anything special, it will go in
/usr/local. Therefore, I find it sensible for a configure-enabled package to
search /usr/local
Don't search /usr/local unless I ask. Don't search /usr/dt
unless I ask.
Then, 100.1% of users will end-up with a full screen configure line.
Otherwise, how do I tell configure NOT to search /usr/local. Say,
for
instance, someone has installed a broken libfoo.a in /usr/local and I don't
want to pick it up.
By giving it a --site-includes, a --site-libraries, or more generally,
a --site-prefixes option, which will take precedence over everything else.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / E.N.S.T. INF C214 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72
75634 Paris cedex 13 Fax. (33) 01 45 81 31 19