Hi folks, sorry if this has been discussed before but was wondering why multilib hasn't been added to stock Slackware64 already, may be included as an optional set of packages or under extra?

It depends on how many people use multilib as to whether it should be included in the distro.

1 members found this post helpful.

Not everyone wants multilib, and the reasons to run it are getting fewer and fewer (now it's typically for either gaming or skype). Since the use case is shrinking, not growing, I doubt we'll ever see an official multilib Slackware. For those who want to run it, they'll need to rely on Eric to continue providing multilib packages.

Personally, I'm running multilib on my desktop (for Virtualbox (not positive this still requires multilib, but it did at the time) and the occasional game with Steam), but I am pure 64bit on my htpc.

2 members found this post helpful.

Some good points, not sure whether multilib is in demand or not. In my case it comes down to compiling/running Wine (as I no longer use Skype) so if I can find or compile a 64 bit Wine package that can run older win32 games I'd switch to a pure 64 bit Slackware.

Don't think you don't need multilib to run VirtualBox.

I had multilib for a while, but 64 bit wine is more trouble than it's worth, because I don't have any programs that require it.
Since I only use wine for 32 bit programs anyway, I've set up a separate 32 bit system for that.
It's more convenient, smaller than multilib, doesn't need extra libs from nvidia and smp kernel is just as fast as 64 bit.
I see no downside, except maybe having to reboot every once in a while.

1 members found this post helpful.

It does not work that way. Multilib will not be added to Slackware64, period.

1 members found this post helpful.

Since you have done all of the (good) work on multilib, it makes me wonder if Patrick needs your consent before he makes a judgement call like that?

Ho ho - I think maybe you need to read the following definition :

https://en.wikipedia.org/wiki/Benevo...tator_for_life

The 10th name from the top : Patrick Volkerding ... !!

He made that call long ago, when I was still developing the 64-bit Slackware port i.e. before it went public. We had discussions about what the 64-bit Slackware should be. In terms of functionality and maintainability.
Multilib was struck off right at the beginning.

According to Virtualbox maintainer on SBo, it does still require multilib, but I am too lazy to test this on my htpc (pure 64bit) to see if it compiles without multilib.

Either way, I made the decision to go multilib on my desktop quite some time ago, and I'll likely stick with it when 14.2 is released.

"I might note that I run 64-bit VirtualBox on 64-bit Slackware (stable), no Multilib...". HERE.

How to do virtualbox HERE not from SBo.

Seems to be a Free Proprietary or Free open source decision.

1 members found this post helpful.

Thanks. I must've forgotten about that post.

If I ever do run pure 64bit on my desktop, then I guess that'll be my only option, but I prefer to install software with SlackBuilds.

That doesn't mean that he couldn't change his mind if there was good reason to (although with 32 bit use decreasing, this is most unlikely but never say "never").

I can go on and on trying to bring the point across, but apparently the message is not heard.
The Slackware64 distribution will remain a pure 64bit OS. Period.