What features/changes would you like to see in future Slackware?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Not to mention so many features are unavailable that it's work to make ruby applications backwards compatible. A lot of the newer ruby gems have problems, or cannot be fully utilized.
Is that even possible??? I know a few packages still use Python2 exclusively and haven't added Python3 support yet (I could be wrong though).
I actually think it is. I do know that PyQt, PyKDE, PyGTK all support Python 3. I checked urwid, dbus-python and notify-python and it looks like they support Python 3 too. So I'm pretty confident that Python 3 will support everything that actually needs to be in Slackware.
Mercurial is one notable program that does not support Python 3; it and Python 2 can be moved to /extra.
I kinda wonder if we move to KDE/Plasma5, if Wayland support (which would pull in libxkbcommon and libinput, and all the XWayland stuff might be worth a try-out?
Sounds good. I have gotten weston built and working on Slackware (and let me pause to say it took a LOT of reworking to do this... ugh! Cairo has to be rebuilt with glesv2 rather than gl, libinput had to be imported, along with libxkbcommon-0.5.0, the proprietary drivers don't work (middle-finger @ nvidia) , rebuilt mesa-10.5.7 with wayland, xorg-server rebuilt with wayland... need I continue? NO!!!) but it does work somewhat, with a few known problems, like Weston refuses to reset the windows and apps each time you close them. I did have to use OpenPAM which luckily worked! Wow... thought that damn thing only used Linux-PAM...
Anyways, due to the fact weston is a P.O.S. I will NOT be uploading it Slackworks... EVER! It's interesting, but at best, it's still crap.
Anyways, maybe I can get KDE rebuilt or Plasma5 imported for wayland...
I like to see Pat fix the package libxml2 seems the from 14.1 patches to current no longer supply the libxml2.a file which I use to build programs with. I just rebuilt it from source but when your trying to build something global for all to build oh well. One more package I will drop on my bitbucket or github.
Any of the onboard chips usually are still Software Mixing only. I only know of a few onboard devices that actually do(did) hardware mixing and usually those chips are the same ones found on actual sound cards such as the Sound Blaster Emu*-series, C-Media OxygenHD, some older AC97 stuff like the Aureal 8810. Just about everything that is a CODEC style chip HDA or AC97 is software mixing only.
By HDA, do you mean specifically Intel HDA? Would something like Realtek ALC1220 have hardware mixing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.