LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-18-2016, 08:29 PM   #46
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351

The bluez-5.x stuff came from Dugan (primarily) and me, and I've been working on new blueman-2.x for over a year (even contributing to it upstream a bit), and the combination of bluez-5.x and blueman-2.x is a huge improvement for me. I'm sure it's nice for many other Slackware users too, but understand that *I* put forth the effort on it because *I* needed it. For the first time in literally years, bluetooth devices work reliably - every time I need them. My experience there along with Pat and other Slackware team members' testing is why bluez-5.x went into -current. If we had known then that pulseaudio would be needed, then I can't say for sure what the decision would have been, but given the positive reception and results from bluez-5, it seemed reasonable to see how pulseaudio would play with Slackware before reverting bluez-5.x.

After experimenting with pulseaudio, primarily from mario's suggestions and testing of what was mostly ppr:kut's work originally, we were pleasantly surprised to find that PA worked well with very few hiccups. As he said in an earlier post somewhere, Pat did a lot of reading and researching on what bothered people most about PA and made sure those issues were solved before it ever hit the -current tree. Even better, it was added in such a way that *not* using it doesn't even require recompiling things - there's absolutely no reason to get all bent out of shape about it being there. If you don't want to use it, then do a bit of research to figure out how to turn it off; otherwise, use it and enjoy it - it just works.

Ultimately, this "most people have no need for it" banter is a bit disheartening. *I* need it. pprkut needs it. Probably other devel team members need it, or at the very least, they recognize that it makes some parts of what they do easier, which certainly approaches "need" as far as I can tell. This sounds a lot like what pprkut already said, but basically, the people doing the actual work on making Slackware decided that pulseaudio was the best way forward for the distribution as a whole. We've *never* made seat-of-the-pants judgments about things of this nature before, and we didn't this time, and we don't intend to start, so this closeted implication of that is pretty damned insulting. Give it a rest or go find another distribution that's more suitable.

Last edited by rworkman; 01-18-2016 at 11:46 PM. Reason: typos
 
22 members found this post helpful.
Old 01-18-2016, 08:30 PM   #47
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351
Oops - double post...

Last edited by rworkman; 01-18-2016 at 08:31 PM. Reason: double post
 
Old 01-18-2016, 11:35 PM   #48
zakame
Member
 
Registered: Apr 2012
Location: Philippines
Distribution: Debian, Ubuntu, Slackware
Posts: 295

Rep: Reputation: 181Reputation: 181
I like PA in that it now lets me seamlessly throw audio from one device to another in near-real time, as opposed to manually maintaining an ~/.asoundrc . It also now makes some tweaking much easier to do (e.g. parametric equalizer with PA and LADSPA) than previously (I'm aware of alsaequal, but I prefer parametric over fixed-band graphic eqs.)

Kudos to @rworkman and team for making sure PA "just works"(TM)
 
6 members found this post helpful.
Old 01-18-2016, 11:54 PM   #49
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by rworkman View Post
The bluez-5.x stuff came from Dugan (primarily) and me, and I've been working on new blueman-2.x for over a year (even contributing to it upstream a bit), and the combination of bluez-5.x and blueman-2.x is a huge improvement for me. I'm sure it's nice for many other Slackware users too, but understand that *I* put forth the effort on it because *I* needed it. For the first time in literally years, bluetooth devices work reliably - every time I need them. My experience there along with Pat and other Slackware team members' testing is why bluez-5.x went into -current. If we had known then that pulseaudio would be needed, then I can't say for sure what the decision would have been, but given the positive reception and results from bluez-5, it seemed reasonable to see how pulseaudio would play with Slackware before reverting bluez-5.x.

After experimenting with pulseaudio, primarily from mario's suggestions and testing of what was mostly ppr:kut's work originally, we were pleasantly surprised to find that PA worked well with very few hiccups. As he said in an earlier post somewhere, Pat did a lot of reading and researching on what bothered people most about PA and made sure those issues were solved before it ever hit the -current tree. Even better, it was added in such a way that *not* using it doesn't even require recompiling things - there's absolutely no reason to get all bent out of shape about it being there. If you don't want to use it, then do a bit of research to figure out how to turn it off; otherwise, use it and enjoy it - it just works.

Ultimately, this "most people have no need for it" banter is a bit disheartening. *I* need it. pprkut needs it. Probably other devel team members need it, or at the very least, they recognize that it makes some parts of what they do easier, which certainly approaches "need" as far as I can tell. This sounds a lot like what pprkut already said, but basically, the people doing the actual work on making Slackware decided that pulseaudio was the best way forward for the distribution as a whole. We've *never* made seat-of-the-pants judgments about things of this nature before, and we didn't this time, and we don't intend to start, so this closeted implication of that is pretty damned insulting. Give it a rest or go find another distribution that's more suitable.
I certainly needed bluez-5.x to support my heart rate monitor via dbus. I'm glad that it was added.
 
8 members found this post helpful.
Old 01-19-2016, 12:14 AM   #50
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,198

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
Quote:
Originally Posted by Richard Cranium View Post
I certainly needed bluez-5.x to support my heart rate monitor via dbus. I'm glad that it was added.
Wow, I would definitely call that an example of mission critical software.
 
4 members found this post helpful.
Old 01-19-2016, 01:14 AM   #51
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by zakame View Post
Kudos to @rworkman and team for making sure PA "just works"(TM)
+1 on that.

Reading through the various PulseAudio-related threads, it looks like there are two types of "conservative" users.
  1. Those who trust Slackware as a conservative distribution, e. g. maintained by a team who won't include any half-baked "technology preview" in an otherwise reliable distribution.
  2. Those who seem to be opposed to any change, whatever it is, and whose epidermic reaction to the sensible introduction of a new feature is a mere "How can I get rid of $NEWFEATURE"?
 
4 members found this post helpful.
Old 01-19-2016, 02:33 AM   #52
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by dugan View Post
Wow, I would definitely call that an example of mission critical software.
[edit: removed]
 
Old 01-19-2016, 03:27 AM   #53
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742
Quote:
Originally Posted by Richard Cranium View Post
[edit: removed]
reported, because I think this is not the way communication in this forum should be
 
6 members found this post helpful.
Old 01-19-2016, 03:29 AM   #54
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
Quote:
Originally Posted by Richard Cranium View Post
[edit: removed]
Dugan was not being sarcastic and you completely mis-interpreted that sentence. Unwarranted reply, not befitting this community.
 
11 members found this post helpful.
Old 01-19-2016, 07:27 AM   #55
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by Richard Cranium View Post
Go fuck yourself, asshole.
Full moon today or what is it?
 
2 members found this post helpful.
Old 01-19-2016, 07:37 AM   #56
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,597

Rep: Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080Reputation: 4080
Richard Cranium, that kind of language isn't acceptable at LQ. If you'd like to continue participating here, please refrain from using it in the future. Thanks.

--jeremy
 
5 members found this post helpful.
Old 01-19-2016, 07:48 AM   #57
bartgymnast
Member
 
Registered: Feb 2003
Location: Almere, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368

Rep: Reputation: 165Reputation: 165
Kudos rworkman,

I am happy to see pulseaudio added to slackware.
It makes indeed my life easier as developer as I was shipping it with the gnome-3.18 + systemd + wayland build
as pulseaudio is activated by dbus, I did not had to recompile it for systemd.

and guess what, my sound still works like before.

next step would be indeed pam
 
4 members found this post helpful.
Old 01-19-2016, 09:05 AM   #58
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,198

Rep: Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307Reputation: 5307
Quote:
Originally Posted by Richard Cranium View Post
[edit: removed]
I see what you said. I wasn't being sarcastic, and I find it strange that you took it that way.
 
1 members found this post helpful.
Old 01-19-2016, 09:19 AM   #59
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
Quote:
Originally Posted by rworkman View Post
................
Ultimately, this "most people have no need for it" banter is a bit disheartening. *I* need it. pprkut needs it. Probably other devel team members need it,
................
Give it a rest or go find another distribution that's more suitable.
Well, that's exactly what makes Slackware a toy distro.

I have nothing against PulseAudio. What bothers me is the decision making process.


Cheers
 
Old 01-19-2016, 09:49 AM   #60
1337_powerslacker
Member
 
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 862
Blog Entries: 9

Rep: Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592
Quote:
Originally Posted by ivandi View Post
Well, that's exactly what makes Slackware a toy distro.

I have nothing against PulseAudio. What bothers me is the decision making process.


Cheers
Slackware's reputation as a stable, reliable distro didn't happen by accident; it was the result of many years of making decisions that have panned out as workable over the long run. Your definition of "toy", as I understand it, is due to some people in the decision-making process including something that you don't consider "professional" for their own benefit. Well, it doesn't impact the overall reliability of the distro. And do you really think that "professional" distros like Red Hat, CentOS, OpenSUSE, and the like just add things for only professional reasons? Do you not think that these people add things to them for their own needs and/or wants?

I have yet to encounter a distro that is as professional as Slackware. In my decade of using it, I have seen nothing about it that makes it a "toy" distro. If, on the other hand, a "toy" is something you define as playing with for fun, then yes, maybe they do, but that's what part of what makes Slackware a fulfilling computing experience, IMHO. And it still doesn't impact the stability. At all.

Happy Slacking!

Regards,

Matt
 
6 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware and Bluetooth: where to begin? kikinovak Slackware 12 10-22-2015 06:00 AM
Slackware on the begin of the qemu advent calendar a4z Slackware 8 12-03-2014 08:42 AM
Setting up a mail server with Slackware: where to begin? kikinovak Slackware 8 09-16-2011 02:00 PM
[SOLVED] Squeeze + Pulseaudio + Alsa and USB Midi device causes Pulseaudio crash mad4linux Debian 1 01-26-2011 03:57 AM
When does the next Slackware developement cycle begin? Old_Fogie Slackware 3 11-05-2006 04:58 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:13 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration