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] rfc: adding sbin directories to PATH for all users
Date: Wed, 25 Nov 2015 22:58:34 -0500	[thread overview]
Message-ID: <CAJ0EP42vAWh5KUkR9+=fPqGfJWUXm=kkonDa2AR7dFe1c7G0ag@mail.gmail.com> (raw)
In-Reply-To: <20151126003957.b2e7acf9daf06c603c2d0195@gentoo.org>

On Wed, Nov 25, 2015 at 4:39 PM, Andrew Savchenko <bircoph@gentoo.org> wrote:
> On Wed, 25 Nov 2015 11:10:11 -0600 William Hubbs wrote:
>> All,
>>
>> I would like for us to discuss adding the sbin directories to PATH for
>> all users.
>>
>> The only reason I can think of that we have removed them is cosmetic (it
>> removes things from tab completion), but I have also heard that having
>> those things in tab completion would be a good thing.
>>
>> Another reason I am bringing this up is this bug [1]. On standard OSx,
>> there is no reason to hard code the path to sysctl like I'm being asked
>> to do in the patch associated with this bug, because the sbin
>> directories are always  in the path. In other words, it isn't worth the
>> effort to send this patch upstream, which means there will always be a
>> Gentoo-specific patch to dev-lang/go unless upstream finds another way
>> to do the test they are doing on OSx via sysctl.
>>
>> Any ideas?
>
> +1. Just do it.
>
> I add /sbin and /usr/sbin in PATH on all Gentoo setups for ages.
> Too many useful tools are there. Though, add them after /bin
> and /usr/sbin for non-priviledged users and before for root.

Swapping the order is silly and should be pointless. If we are
installing different binaries with the same name in bin/sbin, that's a
bug that needs fixing.


      reply	other threads:[~2015-11-26  3:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 17:10 [gentoo-dev] rfc: adding sbin directories to PATH for all users William Hubbs
2015-11-25 17:24 ` Michael Orlitzky
2015-11-25 17:36 ` Kristian Fiskerstrand
2015-11-25 18:05   ` Ulrich Mueller
2015-11-25 18:17     ` Michał Górny
2015-11-25 19:18       ` Daniel Campbell
2015-11-25 19:23         ` Michał Górny
2015-11-25 20:16           ` Mike Gilbert
2015-11-25 20:15             ` Kristian Fiskerstrand
2015-11-26 15:03               ` [gentoo-dev] " Duncan
2015-11-26 15:10                 ` Alan McKinnon
2015-11-25 18:14   ` [gentoo-dev] " William Hubbs
2015-11-25 18:31     ` Ulrich Mueller
2015-11-25 18:38       ` William Hubbs
2015-11-25 18:51         ` Ulrich Mueller
2015-11-25 19:47           ` William Hubbs
2015-11-25 20:53             ` Ulrich Mueller
2015-11-25 21:39               ` William Hubbs
2015-11-25 20:12           ` splite-gentoo
2015-11-25 18:58 ` Mike Gilbert
2015-11-25 20:42   ` Anthony G. Basile
2015-11-26 16:37   ` Peter Stuge
2015-11-25 19:17 ` Nicolas Sebrecht
2015-11-25 21:39 ` Andrew Savchenko
2015-11-26  3:58   ` Mike Gilbert [this message]

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='CAJ0EP42vAWh5KUkR9+=fPqGfJWUXm=kkonDa2AR7dFe1c7G0ag@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