From: N8TM@aol.com
To: dm@reeducation-labor.lcs.mit.edu, egcs@cygnus.com
Subject: Re: Suggestion for --with-local-prefix configure option
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <c37ea7d.36ef0bb1@aol.com> (raw)
Message-ID: <19990331234600.dlk3LvA4dSL_lao3sFDjlN4oqxSZTN51lmEYh1jdc3A@z> (raw)
In a message dated 3/16/99 10:16:13 AM Pacific Standard Time, dm@reeducation-
labor.lcs.mit.edu writes:
> Currently the option always defaults to /usr/local,
> regardless of --prefix. I argue that this default is wrong for most
> cases.
I'll present an inexpert but biased opinion. I have no problem with the
/usr/local default. I let the snapshots go in /usr/local on all systems where
I have the privilege to do so, without having to worry about whether it is a
workable version. I install the "stable" releases in the primary compiler
location for the target, if I have privileges there. The only target I use
where /usr/local is accessible to me and is on the standard search path is
HPUX. But there, I have to play symlink games because there isn't any disk
space in the real /usr/local, not even enough to run applications which need
significant space on /tmp.
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 18:01 N8TM [this message]
[not found] ` < c37ea7d.36ef0bb1@aol.com >
1999-03-16 18:07 ` Jean-Pierre Radley
1999-03-31 23:46 ` Jean-Pierre Radley
1999-03-17 3:57 ` fheitka
1999-03-31 23:46 ` fheitka
1999-03-31 23:46 ` N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-03-17 14:53 Mike Stump
1999-03-17 19:41 ` David Starner
1999-03-31 23:46 ` David Starner
1999-03-31 23:46 ` Mike Stump
1999-03-16 10:14 David Mazieres
1999-03-16 16:14 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
1999-03-17 0:24 ` Bernd Eggink
1999-03-31 23:46 ` Bernd Eggink
1999-03-31 23:46 ` David Mazieres
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=c37ea7d.36ef0bb1@aol.com \
--to=n8tm@aol.com \
--cc=dm@reeducation-labor.lcs.mit.edu \
--cc=egcs@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).