I really rarely ever need 32bit libs for anything, most notably and weird: Steam.

I heard even they are working on a 64bit client, fscking finally, and I really have ideal why this is even a thing in 2019.  Installing steam and arch both require you to use the "runtime" version, that runs at 32bit, and for fsck's sake I cannot think of a good reason why this is.  Everyone complains about it, and in 2019 it *is* still a thing.

There are how-to's how to get Steam to run in "native" mode, but I've never gotten it to work.  Ever.  The 32bit version works fine, but gezus, why still I ask as it pulls in a ton of irrelevant 32bit libs with every install otherwise and Steam, despite their progressive linux support, still does not?!

-mb


On Wed, Jun 19, 2019 at 9:18 PM Matthew Crews <mailinglists@mattcrews.com> wrote:
For those that haven't seen it, Ubuntu 19.10 and derivatives are going
to end official x86 32-bit support. This is not just the end of 32-bit
ISOs though; they are also removing ALL 32-bit packages from their repos.

https://lists.ubuntu.com/archives/ubuntu-announce/2019-June/000245.html

This will have serious ramifications for those that use Ubuntu and want
to use 32-bit software, device drivers, and the like.

For now the best options appear to be:

1. Run your software in a VM, chroot, snap, or container
2. Stay on Ubuntu 18.04 or earlier and do not upgrade
3. Use a different OS altogether.

I'm opting to phase Ubuntu out completely personally.

-Matt

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss