From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "Philippe Gramoullé" <philippe@gramoulle.com>, reiserfs-list@namesys.com
Subject: Re: need opinions from sysadmins on where reiser4progs should install
Date: Mon, 21 Nov 2005 10:07:00 -0800 [thread overview]
Message-ID: <43820CC4.2010205@namesys.com> (raw)
In-Reply-To: <200511211632.17965.vitaly@namesys.com>
Vitaly Fertman wrote:
>On Monday 21 November 2005 10:09, Hans Reiser wrote:
>
>
>>Philippe GramoullИ wrote:
>>
>>
>>
>>>Hello,
>>>
>>>On Sun, 20 Nov 2005 05:07:23 +0100
>>>rvalles <rvalles@es.gnu.org> wrote:
>>>
>>> | When I run make install on something and haven't specified a prefix on
>>> | configure, I expect /usr/local to be used. If I wanted /, I'd have
>>> | specified that on configure time. If it installed in / by default, it
>>> | would, often, hit the "sacred package-system managed area" of the VFS
>>> | tree annoying people like me to a very great extend, so please don't.
>>>
>>>While i totally agree with you for standard packages, well i based my choice
>>>on actual experience of the last past six years of use with reiserfs V3.
>>>
>>>I can't remember how many times i heard Namesys team say " Install the latest
>>>& greatest reiserfsck", how many times distro thought they knew reiserfsprogs
>>>internals better than Namesys and customized it to the point where it would
>>>eventually break.
>>>
>>>Of course, i can live with a manual install of reiser(fs|4)progs, so i don't
>>>really mind, but talking of support, it can make quite a difference to Namesys
>>>in terms of support, and annoyance with bug reports that could have been easily
>>>avoided.
>>>
>>>
>>>
>>>
>>Ok, I propose the following: search the standard locations for where it
>>is currently, tell the user, ask the user if they want to rename those
>>
>>
>
>the proper service is already done in package managers. if one needs it,
>he can use one of them.
>
>
>
>>versions to *.old if the install of the new one succeeds, and then
>>
>>
>
>this breaks the installed software consistency and may screw the package
>manager up...
>
>
Sigh, good point, ok, well then at least warn the user about them.
>
>
>>prompt for the install location with /sbin as the suggested default. I
>>think that unlike other user installed programs, fsck does not belong in
>>/usr/local. I think Philippe's point that old versions are dangerous is
>>quite valid.
>>
>>
>
>install to the system default through a system package manager;
>
>install to the local default from source to not break the system installed
>software consistency;
>
>
So the reason for not installing to /sbin is to avoid messing up the
package manager? I regret to say it makes sense. If that is the
reason, then warn the user please about old versions left intact, and
suggest they be removed, and prompt the user for the path to install to
and remind them to update their $PATH.
>provide a way to install where a user wants if he knows what he does and
>if he remembers what and how has been installed on a particular system;
>
>
>
>>>Final decision will still be Namesys call, but hopefully this whole thread gave
>>>them some valuable input to make the best decision.
>>>
>>>Thanks,
>>>
>>>Philippe
>>>
>>>
>>>
>
>
>
next prev parent reply other threads:[~2005-11-21 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051120040723.GA1392@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-20 11:55 ` need opinions from sysadmins on where reiser4progs should install 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 [this message]
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
2005-11-13 7:17 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
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
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=43820CC4.2010205@namesys.com \
--to=reiser@namesys.com \
--cc=philippe@gramoulle.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.