From: prj@po.cwru.edu (Paul Jarc)
To: Hans Reiser <reiser@namesys.com>
Cc: Clifford Beshers <clifford.beshers@linspire.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: need opinions from sysadmins on where reiser4progs should install
Date: Thu, 17 Nov 2005 01:01:22 -0500 [thread overview]
Message-ID: <m37jb7olrr.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <437C0D7C.6090502@namesys.com> (Hans Reiser's message of "Wed, 16 Nov 2005 20:56:28 -0800")
Hans Reiser <reiser@namesys.com> wrote:
> Clifford Beshers wrote:
>> http://www.pathname.com/fhs/pub/fhs-2.3.html#SBINSYSTEMBINARIES
>
> well, this says /sbin as I read it. Thanks for the URL Clifford!
The FHS doesn't specify what the default installation prefix for a
source tarball should be. That section says that distributions should
install certain things in /sbin or /usr/sbin, and that admins who
install similar things independently of the distribution should use
/usr/local/sbin. Obviously that doesn't work in some cases, but that
is what the FHS says: distributions and admins should choose those
respective locations, regardless of the package's default.
Since distributions' installations are typically automated and so can
easily specify a non-default prefix, source tarballs generally default
to /usr/local for the admins. As a result, admins will expect the
default to be /usr/local, and they know how to use --prefix=/ if
that's what they want. The principles of least surprise and least
damage suggest that the default for reiser4progs should be /usr/local,
just like every other package, *even if that means the default will
rarely be used*.
For myself, I only care that an explicit --prefix is used for every
installed file, since I install to a different directory anyway.
paul
next prev parent reply other threads:[~2005-11-17 6:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 7:17 need opinions from sysadmins on where reiser4progs should install Hans Reiser
2005-11-13 11:08 ` Petteri Räty
2005-11-13 15:37 ` Gorazd Golob
2005-11-13 17:42 ` Clifford Beshers
2005-11-17 4:56 ` Hans Reiser
2005-11-17 6:01 ` Paul Jarc [this message]
2005-11-14 20:50 ` Tom Vier
2005-11-14 22:26 ` Hubert Chan
2005-11-17 16:06 ` Philippe Gramoullé
2005-11-20 4:07 ` rvalles
[not found] <20051120040723.GA1392@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-20 11:55 ` Philippe Gramoullé
2005-11-21 7:09 ` Hans Reiser
2005-11-21 7:33 ` Hubert Chan
2005-11-21 13:32 ` Vitaly Fertman
2005-11-21 18:07 ` Hans Reiser
2005-11-22 0:04 ` michael chang
2005-11-22 19:33 ` David Masover
2005-11-22 20:14 ` Hubert Chan
2005-11-25 16:54 ` Chester R. Hosey
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=m37jb7olrr.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=clifford.beshers@linspire.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.