any reason why Slackware can't keep ALSA while adapting PulseAudio?
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.
any reason why Slackware can't keep ALSA while adapting PulseAudio?
I've been reading the threads about recent PulseAudio development on slackware. One thing that's unclear to me is why Slackware needs to drop ALSA to support PulseAudio. can't developers keep both and let user decide which one to use?
being a former Debian user, I've been trying out different non-systemd distros, Slackware being one of them. does this move mean eventually Slackware will use SystemD like Debian?
I've been reading the threads about recent PulseAudio development on slackware. One thing that's unclear to me is why Slackware needs to drop ALSA to support PulseAudio. can't developers keep both and let user decide which one to use?
Actually, PulseAudio on Slackware won't even work if ALSA support is removed. We are not taking away anyone's choice of which sound system to use, just setting a default upon installation.
Quote:
being a former Debian user, I've been trying out different non-systemd distros, Slackware being one of them. does this move mean eventually Slackware will use SystemD like Debian?
This has absolutely zero to do with systemd. PulseAudio is not a systemd canary.
One thing that's unclear to me is why Slackware needs to drop ALSA to support PulseAudio.
It didn't.
Quote:
can't developers keep both and let user decide which one to use?
They did.
Where did your confusion come from?
And if Slackware ever adopts systemd, it would probably be the single most carefully-considered decision in the distribution's history. For that reason alone, I'm not worried.
I did already rebuild some of these things, locally, but I don't have disk space or memory to build qt/kde.
If qt will be linked in the future I may have to remove smplayer and a few more packages.
SDL - Done
Phonon - Removed
GStreamer - Downgraded to 0.10
MPlayer - Done
etc - ??
qt - ??
kde - Depends on Phonon/Removed
xfce4 - Done
Yeah, ALSA is the audio drivers and subsequent utilities, runtimes, and other libraries.
PulseAudio is an audio playback and routing server (think of it more like Xorg, dhcp, or apache) that manages audio input and output ports, connections, etc.
It's not my most favorite software, but it works and makes dealing with audio setups less stressful.
Actually, PulseAudio on Slackware won't even work if ALSA support is removed. We are not taking away anyone's choice of which sound system to use, just setting a default upon installation.
This has absolutely zero to do with systemd. PulseAudio is not a systemd canary.
Thanks for the information Patrick, i can sleep relaxed!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
