On 06/01/17 13:33, Stephen Gallagher wrote:
On 01/06/2017 08:04 AM, Jakub Jelinek wrote:
On Thu, Jan 05, 2017 at 03:08:21PM -0800, Brendan Conoboy wrote:
For anyone who isn't familiar with this topic, you might find Debian's
documentation useful:
https://wiki.debian.org/Multiarch
One could take it a step further and actually have target triplets the
convey OS version of the libraries instead of the generic "-redhat-linux"
part of the tuple. With a little rpath abuse apps compiled for F25 could
find their shared libraries in an F25 specific directory and multiple
versions of the same package could be installed at the same time, for
different OS versions. This goes beyond Fedora, too: apps compiled for
Debian could find their shared libraries in a Debian specific directory,
even though it's a Fedora system that is booted. A lot of fiddly details
and hand waving go here, but the end result would be really useful.
Noo! Debian Multiarch is FHS incompatible, too ugly to live with and
doesn't bring benefits, it is just different.
Please don't introduce this into Fedora.
I added it to this list because it came up several times in the earlier thread.
I'm not sold on it. I'm CCing the people who suggested it directly to ask them
to chime in with what advantages they feel it would provide.
So to be honest I hadn't really expected Fedora to make the change but
it was certainly the first thing that came to mind from the email subject.
If we were starting now to support multilib then I would certainly
suggest that the Debian design is the better one but whether it's enough
of an improvement to merit the pain of changing is a rather different
question.
My reasons for thinking it's better are much the same as what other
people have already said - that it treats all arches as equals and
scales readily to whatever is needed rather than just bolting on a
single 32/64 bit split as a kind of special case.
Tom
--
Tom Hughes (tom@xxxxxxxxxx)
http://compton.nu/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
