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.
The advantage of including Pulseaudio in Slackware instead of leaving it on SBo is so that the rest of Slackware's applications and libraries can come built with support for it. MPlayer, for example.
the PA protocol is just "write to pipe" (i suspect dbus, haven't confirmed)
there is no performance difference between going through the alsa plugin vs "native"
i tested
Click here to see the post LQ members have rated as the most helpful post in this thread.
Yes, but also if you learn to set up ALSA properly, you don't really need PulseAudio.
~/.asoundrc and /etc/modprobe.d/alsa.conf are very powerful files to have and use, and can do fairly much the same things PulseAudio does, but it takes reading documentation, learning ALSA configuration syntax, and some trial and error before it works and you never have to set it up again.
Pulse isn't even a hard requirement for anything except Skype anyway, so one less package to deal with. And yes, for the networked audio we still have ESounD... all of which are the bare, yet functional, minimums.
And still, Alsa can not reroute audiostreams on the fly, so even if you are a master in configuring it it won't do that, you need something like Pulseaudio for that.
When this gets released to open source to go along with LLDB and Clang, let's get this one in there and find out if this can really eventually take the place of C (!!!)
Just a kind reminder not to ask for it, after seeing leo's post, but... fairly much, LLVM/Clang and GCC are interchangeable to a point, but the Linux kernel requires a LOT of patches to build with LLVM/Clang, and it still requires parts of GCC at times.
The only problem is LLVM/Clang isn't tested really for building entire sets of software except on FreeBSD, not Linux. For Slackware to gain LLVM/Clang as a default compiler, to paraphrase Jigsaw "Oh yes... there will be patches." and I doubt the people who are contributing at SBo and our leaders here at Slackware wish to hunt down patches in record numbers just to do this.
When this gets released to open source to go along with LLDB and Clang, let's get this one in there and find out if this can really eventually take the place of C (!!!)
don't you think that swift without cocoa is similar crippled as dot net without the gui stuff ...
Very true. However, by comparison, llvm/clang is noted to have better read-outs when there are errors and such. I wonder how much of Slackware could be built with llvm/clang without penalty and problem. FreeBSD switched due to licenses as well.
As far as C being replaced? No way. C is the universal coding language.
I'd like to see Python 2 properly replaced with Python 3 (all Python files included work with Python 3, everything linked against the Python libraries are linked against Python 3). But I don't want that for the next version of Slackware. I want it for the next version after that.
ConsoleKit2-0.9.2 getting added would be welcome. Apparently there are still some lingering issues with ConsoleKit-0.4.2 that still spark some problems with xfce4-power-manager and upower-0.9.23.
Quote:
Originally Posted by dugan
I'd like to see Python 2 properly replaced with Python 3 (all Python files included work with Python 3, everything linked against the Python libraries are linked against Python 3). But I don't want that for the next version of Slackware. I want it for the next version after that.
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).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
