I want to gauge how other slackers feel about multilib and future releases of Slackware.

Since there are separate packages maintained by Alien Bob (which are excellent!) you could just download and install multilib packages from his page on slackware.com

Given that there is a need for some Slackware users out there that would need a multilib based system because of drivers, or applications that are not available in 64-bit (skype comes to mind), thus the need for multilib.

So I am wondering if multilib should in some way be included in the next release, or at least considered.

Maybe including it in /extra since I am not suggesting it be part of the actual installation itself. Just a thought.

I think 32-bit only programs are on their way out, so I'd say downloading it from Alien Bob's site is fine.

1 members found this post helpful.

Having them in extra could make it more difficult for things like slackpkg+ to keep them up-to-date without causing conflicts. I vote for keeping them on Alien Bob's site.

1 members found this post helpful.

And multilib would be too big to keep it under /extra

2 members found this post helpful.

I don't use it. Just about every application on Linux can be built for 32-bit and 64-bit, and I don't use WINE. AlienBOB's repository is fine, but it's not needed for /extra nor needed during installation as an option. Adding it will only increase the size of the ISO, and honestly, we need to find ways to reduce that rather than increase it.

1 members found this post helpful.

And since Pat wants slackware64 to remain a pure 64-bit OS, you'll have to bear with me and my repository.

Eric

6 members found this post helpful.

FYI and OT, Eric's multilib has other uses. I've been experimenting on Eric's multilib gcc with distcc to compile i486, i686 and x86_64 on an x86_64 server without setting up a cross toolchain -- it mostly works I'll do a writeup if I get the time to fix the last few problems...

1 members found this post helpful.

As a hardcore wine-gamer, I would love to see it in the official repos. But it's not a must.

2 members found this post helpful.

IMHO I would leave it the way it is now. As mentioned before slackpkg+ works great with the current setup. of course this All depends if Eric continues his great support of his repo.

2 members found this post helpful.

I voted to continue to have multi-libraries on Alien Bob's site. I don't currently run multi-libraries on my Slack64 boxes, but, I am very happy that Eric is willing to maintain this software.

1 members found this post helpful.

I picked: I don't need multilib, I don't really care, but I agree with the above statement.

1 members found this post helpful.

I use multilib on a couple of machines. I am fine with the way it is. Thank you Alien Bob for all that you do!

It wouldn't bother me if it was included as an option of the DVD or in extra. But the DVD "is" getting crowded.

One of the many reasons I use Slackware, is Slackware64 is pure 64-bit and I really like that. Most other distributions are a mixed bag with no choice. If I need compatibility with 32-bit programs I can add it and tailor it to my specific needs.

I mirror multilib locally (do the same with ktown and my own set of packages) to speed things up a bit when upgrading across my LAN. Today I set up Slackpkg+ for the first time. Wow! Why did I wait so long to do this? Thank you zerouno!

1 members found this post helpful.

The Slackware64 14.1 ISO is currently at 2.3GB, so I don't think it is crowded or needs to be reduced in size. Anyways, rather than putting multilib into /extra it would be easier to just put slackpkg+ there, so that anyone who wants to go the multilib route can easily do that.

1 members found this post helpful.

2.3 GB is still large enough, and that's due to the /source being moved to it's own DVD.

Slackpkg+ would be a great addition. Sbotools from Slackbuilds.org would be a nice addition as well.

What I would like to see (my personal opinion remember - Pat will not agree) is that gcc and glibc in Slackware64 will be built multilib-capable, the rest of the system can stay pure 64-bit. You do not need _anything_ outside of the stock Slackware64 to enhance glibc and gcc with 32-bit support. This would make it less intrusive to create a full multilib system - all you'd need to add would be the compat32 packages.

And yes, having sbopkg in Slackware and slackpkg+ added as well would be cool. But those are easy to add by Slackware users at least.

Eric

2 members found this post helpful.