On Thursday, January 5, 2017, Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote:
On 01/05/2017 11:03 AM, Stephen Gallagher wrote:
> # Overview
>
> For many years, Fedora has supported multilib by carrying parallel-installable
> libraries in /usr/lib[64]. This was necessary for a very long time in order to
> support 32-bit applications running on a 64-bit deployment. However, in today's
> new container world, there is a whole new option.
>
> I'd like to propose that we consider moving away from our traditional approach
> to multilib in favor of recommending the use of a 32-bit container runtime when
> needed on a 64-bit host.
>
So, this thread provided a lot of feedback. I had anticipated that the
suggestion would not be universally accepted, but I didn't quite expect quite
so... vehement a response. :-)
I'll attempt to summarize the conversation thus far:
* By far, the most frequent concern was that it would break Wine and Steam.
* Third-party software written only for 32-bit runtimes would likely require
considerable hacking to continue working under such a system.
* Cross-compilers wouldn't be able to work with this system without significant
modification.
Two suggestions were raised as alternatives to the container approach:
* Switch to using the Debian style of multi-arch layout, which instead of
/usr/lib and /usr/lib64 uses /usr/lib/$ARCH-linux-gnu. Benefits to this would
include the emergence of a de-facto standard for system layout between the major
distributions.
* Ship only one arch in the repositories and allow users to trivially enable the
repositories for other arches through DNF if they have need.
* Keep things as they are, which means things keep to "just work" (tm)
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
