On Sun, Apr 10, 2016 at 7:55 AM, Joshua Kinard <ku...@gentoo.org> wrote:
>
> Create like, a table on the Wiki or some kind of metadata property per-package
> that can contain a boolean or tri-state flag indicating whether it works or
> doesn't work (or kinda works) on split-usr. Or a tracker on Bugzie.
> Something.
>
I'm sure there will be a tracker for packages that don't work on a
merged /usr. (We are already on a split /usr.)
Honestly, I'm still not quite sure why we're even having this
discussion. I don't think anybody actually intends to make any
changes at all. If they do, they should issue some kind of plan and
indicate what they're looking for from everybody else.
Such as: "Hello, I help maintain baselayout and I intend to change
/(s)lib and /(s)bin and /usr/sbin into symlinks to /usr/bin and move
all the files into those directories there. To test this out now
please do xyz, and report any bugs against tracker #123456."
Or: "Hello, I help maintain baselayout and I just introduced a new USE
flag which does ... I think it is something you should try out. Bugs
can be reported at..."
Or: "Hello, I think the baselayout maintainers are idiots and I just
introduced librelayout which does ... You should definitely switch
because only losers run with a split /usr. Bugs can be reported at...
Oh, and my fancy librelayout doesn't need gen_usr_ldscript so I
select_one_of('won't lift a finger to keep it working', 'will just
laugh at the folks who are wasting their time keeping it working')."
It seems to me that we're just having a general discussion about the
pros/cons of a /usr merge. That is nice, but people are getting
worked up because they think that somehow whoever "loses" this
"discussion" will get something shoved down their throats or won't be
able to have something nice.
Almost every big change that has become popular in Gentoo just started
out as another alternative, and support grew organically. I don't
really see the need to reach some kind of consensus here. I'd love to
have an option of a /usr merge and a migration path. I'd love to see
it as the default, but that is a different discussion, and if it is
optional then it is also a less contentious discussion whichever way
it goes.
--
Rich
