1 |
On Sun, Jul 14, 2019 at 9:49 PM Michael Orlitzky <mjo@g.o> wrote: |
2 |
> |
3 |
> On 7/14/19 7:50 PM, Mike Gilbert wrote: |
4 |
> > |
5 |
> > +# Mike Gilbert <floppym@g.o> (2019-07-14) |
6 |
> > +# Enable split-usr by default to keep systems working. |
7 |
> > +USE="${USE} split-usr" |
8 |
> |
9 |
> A mandatory USE="keep-working" raises some philosophical red flags for |
10 |
> me. |
11 |
|
12 |
Yeah, that wording is bad. Maybe something like: |
13 |
|
14 |
# Maintain split /usr for existing installs. |
15 |
|
16 |
> Wouldn't it be better to name the flag "merge-usr" and leave the |
17 |
> profile alone? |
18 |
|
19 |
The "split-usr" flag is already being used by a few packages, so I |
20 |
would like to keep it. |
21 |
|
22 |
Another way to think about it: in the merged /usr case, ebuilds |
23 |
generally do not need to do anything special: they can just copy their |
24 |
files to $prefix (/usr). In the split /usr case, ebuilds need to do |
25 |
special stuff like passing extra configure flags (--bindir, --libdir), |
26 |
or calling gen_usr_ldscript to move libraries around. |
27 |
|
28 |
The "split-usr" USE flag enables this special stuff. Having a |
29 |
"merged-usr" USE flag would invert the meaning: disable the special |
30 |
stuff if the flag is enabled. We generally try to avoid inverted flags |
31 |
like this (a notable exception being the "vanilla" USE flag). |
32 |
|
33 |
> (This will be especially bad for the people who start with USE="-*") |
34 |
|
35 |
As has been previously mentioned, we don't generally recommend this |
36 |
for people who don't know what they are doing. In any case, I think |
37 |
they would have already run into problems given that baselayout has |
38 |
had IUSE="+split-usr" for at least several months. |
39 |
|
40 |
A possible solution would be to add split-usr to use.force in the base |
41 |
profile, and un-force it in some new profile we create at a later |
42 |
date. Do people think this is warranted? |