From: David Seifert <soap@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin'
Date: Tue, 15 Oct 2019 14:00:29 +0200 [thread overview]
Message-ID: <da5bfc1b9aa3edd71276c5ecec8d92b35f18fb8c.camel@gentoo.org> (raw)
In-Reply-To: <CAJ0EP40a6nTHU5h5ykZmqHU94bsT8xTopPMX9CJchvPCCQoLCA@mail.gmail.com>
On Sun, 2019-10-13 at 12:33 -0400, Mike Gilbert wrote:
> On Sat, Oct 12, 2019 at 1:52 PM David Seifert <soap@gentoo.org>
> wrote:
> > On Sat, 2019-10-12 at 19:01 +0200, Dennis Schridde wrote:
> > > On Samstag, 12. Oktober 2019 18:02:28 CEST William Hubbs wrote:
> > > > On Sat, Oct 12, 2019 at 01:11:49PM +0200, Michał Górny wrote:
> > > > > On Sat, 2019-10-12 at 13:00 +0200, David Seifert wrote:
> > > > > > * Some distros have not just merged / and /usr, they
> > > > > >
> > > > > > have also merged /usr/bin and /usr/sbin. By giving
> > > > > > users the choice of merging */bin and */sbin,
> > > > > > Gentoo follows suit.
> > > > >
> > > > > What about the scenario when /bin has been merged with
> > > > > /usr/sbin
> > > > > and /sbin with /usr/bin? ;-P
> > > >
> > > > I also don't see the need for something like this. The idea of
> > > > the
> > > > /usr
> > > > merge is to have all binaries available in one place, and there
> > > > really
> > > > is not a good justification for separating bin from sbin.
> > >
> > > Do I read this correctly? USE=-split-usr currently means that
> > > /bin,
> > > /sbin, /
> > > usr/bin and /usr/sbin point to the same directory?
> > >
> > > If that is not the case, then I agree that users should have the
> > > possibility
> > > to set it up like this and USE=-split-sbin should be supported.
> > >
> > > --Dennis
> >
> > I agree, I wasn't aware that USE=-split-usr implies the complete 2-
> > level (/usr and *sbin) merge. In that case, all of this is
> > obsolete.
>
> That was NOT my intention when I introduced the split-usr USE flag.
>
> For bin/sbin, I would prefer to drop any conflicting links
> unconditionally. Do you have examples of scenarios where this is not
> possible?
>
William has confirmed on IRC that USE=-split-usr performs the complete
Fedora-esque /usr merge (which makes sense IMO).
next prev parent reply other threads:[~2019-10-15 12:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 11:00 [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin' David Seifert
2019-10-12 11:11 ` Michał Górny
2019-10-12 16:02 ` William Hubbs
2019-10-12 17:01 ` Dennis Schridde
2019-10-12 17:52 ` David Seifert
2019-10-13 16:33 ` Mike Gilbert
2019-10-13 16:43 ` Mike Gilbert
2019-10-13 17:38 ` Michał Górny
2019-10-15 12:00 ` David Seifert [this message]
2019-10-15 16:02 ` Mike Gilbert
2019-10-15 16:04 ` Mike Gilbert
2019-10-15 17:34 ` David Seifert
2019-10-16 3:08 ` Joshua Kinard
2019-10-16 15:39 ` William Hubbs
2019-10-16 17:17 ` Ulrich Mueller
2019-10-16 18:19 ` William Hubbs
2019-10-17 6:59 ` Ulrich Mueller
2019-10-19 23:36 ` Joshua Kinard
2019-10-16 9:18 ` Jaco Kroon
2019-10-16 9:48 ` David Seifert
2019-10-16 10:03 ` Jaco Kroon
2019-10-16 10:38 ` Michał Górny
2019-10-16 16:06 ` 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=da5bfc1b9aa3edd71276c5ecec8d92b35f18fb8c.camel@gentoo.org \
--to=soap@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