public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] newsitem: baselayout 2.5 changes
Date: Thu, 8 Feb 2018 15:55:02 -0500	[thread overview]
Message-ID: <CAJ0EP42sG4w6kYcSuBreV8JL=titcEGQhmh272UEFQC2v+BXHQ@mail.gmail.com> (raw)
In-Reply-To: <23164.46578.955475.114066@a1i15.kph.uni-mainz.de>

On Thu, Feb 8, 2018 at 3:41 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Thu, 8 Feb 2018, Mike Gilbert wrote:
>
>> Eliminating ROOTPATH seems like a significant change. Was this
>> officially discussed somewhere that I missed?
>
>> I actually support the change, but other people should be given the
>> chance to complain about it on the record.
>
> It contradicts the FHS, which says that /sbin contains "root-only
> commands" and that "ordinary users should not have to place any of the
> sbin directories in their path." [1]

That would be fine if we actually followed the recommendation
mentioned in the first half of that footnote.

"Deciding what things go into "sbin" directories is simple: if a
normal (not a system administrator) user will ever run it directly,
then it must be placed in one of the "bin" directories."

However, there are plenty of examples of commands that normal users
may run from sbin. Moving these commands often causes problems for
packages that either hard code absolute paths, or detect paths at
build time. I think it would be less disruptive to add sbin to PATH
than it would be to try and "fix" all the packages that install
commands in the wrong place.


  reply	other threads:[~2018-02-08 20:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 19:52 [gentoo-dev] newsitem: baselayout 2.5 changes William Hubbs
2018-02-08 20:16 ` Mike Gilbert
2018-02-08 20:41   ` Ulrich Mueller
2018-02-08 20:55     ` Mike Gilbert [this message]
2018-02-08 22:13       ` William Hubbs
2018-02-08 22:17         ` M. J. Everitt
2018-02-08 22:33           ` Rich Freeman
2018-02-08 22:49             ` Michael Orlitzky
2018-02-08 23:12               ` William Hubbs
2018-02-08 23:25                 ` Michael Orlitzky
2018-02-09  0:03                   ` Rich Freeman
2018-02-08 22:33           ` William Hubbs
2018-02-08 22:43             ` M. J. Everitt
2018-02-18  1:59             ` Benda Xu
2018-02-08 22:20         ` Michael Orlitzky
2018-02-10 10:49       ` Mike Auty
2018-02-10 10:55         ` Michał Górny
2018-02-10 15:34 ` [gentoo-dev] " Duncan
2018-02-10 18:15   ` William Hubbs
2018-02-10 18:43     ` William Hubbs
2018-02-12  6:19       ` Duncan
2018-02-12  6:38     ` Duncan
2018-02-18  2:07 ` [gentoo-dev] " Benda Xu
2018-02-20 18:49   ` William Hubbs

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='CAJ0EP42sG4w6kYcSuBreV8JL=titcEGQhmh272UEFQC2v+BXHQ@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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