Mailing List Archive

[PATCH 2/6] profiles: enable USE="split-usr" in base
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
---
profiles/base/make.defaults | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/profiles/base/make.defaults b/profiles/base/make.defaults
index 3fdd2e453a46..80c5852277f4 100644
--- a/profiles/base/make.defaults
+++ b/profiles/base/make.defaults
@@ -115,6 +115,10 @@ USE="${USE} cxx"
# https://archives.gentoo.org/gentoo-dev/message/ba0e3457e4b807e79816f0df03566af0
USE="${USE} xattr"

+# Mike Gilbert <floppym@gentoo.org> (2019-07-14)
+# Enable split-usr by default to keep systems working.
+USE="${USE} split-usr"
+
# Tiziano Müller <dev-zero@gentoo.org> (2010-01-24)
# We usually don't want python to (re)write .py[co] files during phase runs
# since it could cause sandbox violations
--
2.22.0
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On 7/14/19 7:50 PM, Mike Gilbert wrote:
>
> +# Mike Gilbert <floppym@gentoo.org> (2019-07-14)
> +# Enable split-usr by default to keep systems working.
> +USE="${USE} split-usr"

A mandatory USE="keep-working" raises some philosophical red flags for
me. Wouldn't it be better to name the flag "merge-usr" and leave the
profile alone? (This will be especially bad for the people who start
with USE="-*")
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On Sun, Jul 14, 2019 at 09:49:00PM -0400, Michael Orlitzky wrote:
> On 7/14/19 7:50 PM, Mike Gilbert wrote:
> >
> > +# Mike Gilbert <floppym@gentoo.org> (2019-07-14)
> > +# Enable split-usr by default to keep systems working.
> > +USE="${USE} split-usr"
>
> A mandatory USE="keep-working" raises some philosophical red flags for
> me. Wouldn't it be better to name the flag "merge-usr" and leave the
> profile alone? (This will be especially bad for the people who start
> with USE="-*")

The people who start with USE="-*" are already on their own, we have
many use flags we turn on in make.defaults in the profiles.

The ultimate goal is to turn this flag off in the 19.0 profiles, we are
just preserving the current status in the earlier ones.

William
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
Am Montag, 15. Juli 2019, 03:49:00 CEST schrieb Michael Orlitzky:
>(This will be especially bad for the people who start
> with USE="-*")

Not recommended, not supported. Garbage in, garbage out.

--
Andreas K. H?ttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On 7/14/19 10:02 PM, Andreas K. Huettel wrote:
> Am Montag, 15. Juli 2019, 03:49:00 CEST schrieb Michael Orlitzky:
>> (This will be especially bad for the people who start
>> with USE="-*")
>
> Not recommended, not supported. Garbage in, garbage out.
>

Nothing In, Garbage Out.
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On 7/14/19 9:56 PM, William Hubbs wrote:
>
> The ultimate goal is to turn this flag off in the 19.0 profiles, we are
> just preserving the current status in the earlier ones.
>

So, to be clear: the plan is to force a /usr merge after all?
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On Mon, Jul 15, 2019 at 10:33 AM Michael Orlitzky <mjo@gentoo.org> wrote:
>
> On 7/14/19 9:56 PM, William Hubbs wrote:
> >
> > The ultimate goal is to turn this flag off in the 19.0 profiles, we are
> > just preserving the current status in the earlier ones.
> >
>
> So, to be clear: the plan is to force a /usr merge after all?
>

I don't anticipate that happening within 2019, so I doubt it would be
turned off in a "19.0" profile.

I think Gentoo developers are rather split on the /usr merge, and I
suspect a council ruling will be necessary if the pro-usr-merge camp
wants to push it through.
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On Sun, Jul 14, 2019 at 9:49 PM Michael Orlitzky <mjo@gentoo.org> wrote:
>
> On 7/14/19 7:50 PM, Mike Gilbert wrote:
> >
> > +# Mike Gilbert <floppym@gentoo.org> (2019-07-14)
> > +# Enable split-usr by default to keep systems working.
> > +USE="${USE} split-usr"
>
> A mandatory USE="keep-working" raises some philosophical red flags for
> me.

Yeah, that wording is bad. Maybe something like:

# Maintain split /usr for existing installs.

> Wouldn't it be better to name the flag "merge-usr" and leave the
> profile alone?

The "split-usr" flag is already being used by a few packages, so I
would like to keep it.

Another way to think about it: in the merged /usr case, ebuilds
generally do not need to do anything special: they can just copy their
files to $prefix (/usr). In the split /usr case, ebuilds need to do
special stuff like passing extra configure flags (--bindir, --libdir),
or calling gen_usr_ldscript to move libraries around.

The "split-usr" USE flag enables this special stuff. Having a
"merged-usr" USE flag would invert the meaning: disable the special
stuff if the flag is enabled. We generally try to avoid inverted flags
like this (a notable exception being the "vanilla" USE flag).

> (This will be especially bad for the people who start with USE="-*")

As has been previously mentioned, we don't generally recommend this
for people who don't know what they are doing. In any case, I think
they would have already run into problems given that baselayout has
had IUSE="+split-usr" for at least several months.

A possible solution would be to add split-usr to use.force in the base
profile, and un-force it in some new profile we create at a later
date. Do people think this is warranted?
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
On 7/15/19 11:22 AM, Mike Gilbert wrote:
>
> The "split-usr" flag is already being used by a few packages, so I
> would like to keep it.

The merits of the usr-merge notwithstanding, this does make more sense
if the plan is to eventually drop the flag entirely.


>> (This will be especially bad for the people who start with USE="-*")
>
> As has been previously mentioned, we don't generally recommend this
> for people who don't know what they are doing. In any case, I think
> they would have already run into problems given that baselayout has
> had IUSE="+split-usr" for at least several months.
>
> A possible solution would be to add split-usr to use.force in the base
> profile, and un-force it in some new profile we create at a later
> date. Do people think this is warranted?
>

I understand saying "you're on your own" to people who set USE="-*", but
in practice it's the best-supported way to turn off the
constantly-changing set of maintainers' pet IUSE defaults. I suppose we
can at least agree that some people do it. If there's a way to proceed
that doesn't break their systems by surprise one morning, it'd be the
polite thing to do.
Re: [PATCH 2/6] profiles: enable USE="split-usr" in base [ In reply to ]
? ??, 15/07/2019 ? 11:06 -0400, Mike Gilbert ?????:
> On Mon, Jul 15, 2019 at 10:33 AM Michael Orlitzky <mjo@gentoo.org>
> wrote:
> > On 7/14/19 9:56 PM, William Hubbs wrote:
> > > The ultimate goal is to turn this flag off in the 19.0 profiles,
> > > we are
> > > just preserving the current status in the earlier ones.
> > >
> >
> > So, to be clear: the plan is to force a /usr merge after all?
> >
>
> I don't anticipate that happening within 2019, so I doubt it would be
> turned off in a "19.0" profile.
>
> I think Gentoo developers are rather split on the /usr merge, and I
> suspect a council ruling will be necessary if the pro-usr-merge camp
> wants to push it through.
>

A little offtop: is there a tracker bug for /usr merge related issues?
I can't find one.