So, there is PulseAudio... How about to begin investigating adding LinuxPAM to Slackware too?
 

Then, Slackware is no "virgin" anymore, as our resident Purists want, it becoming a "modern, relevant" Linux distro in the Town. ;)

Then, why not to include LinuxPAM, too?

You known, that minimal set, letting the "cancer" to propagate update after update...

Hi Darth Vader, one step at the time please :-) When your target audience is putting the axe into both your legs the chances for tripping over are a lot bigger.

The only reason we have pulseaudio is bluez requiring it. If Patrick could find an alternative to this, I'm going to take a shot in the dark guess, he'd have found it, and used it by now.

Not only an axe into both legs, but sitting on a branch and sawing it off while you sit on it isn't the best of ideas either.

This.

And the very start of the beta is obviously the wrong time to "investigate" adding PAM.

QOTD right there. :-)

And what exactly makes you think Slackware isn't a "virgin" anymore? Just because it added Pulseaudio makes it any more or less of itself? Sorry, but Slackware has always only added dependencies as required by the packages it contains, upgrades, and continues to use as Patrick sees fit.

Xfce 4.10 should have been a clue to this when it pulled back in a lot of Gnome stuff to resolve dependencies for it.

And yes, Slackware 14.2 is at beta so let's focus on helping Patrick in ironing out bugs, not opening cans spilling worms everywhere.

there is no axe in any leg with PA, but things will work better, like putting the notebook to the TV and just switch the sound, as it works with any other distro since long time now out of the box.
and with PAM would be the same, most would not even notice it, and some will make a short cry and eventually repeating some technical nonsense.

Please .. that ship sailed with the transition from libc5 to glibc ;-)

Exactly the same phrase was used by the systemd proponents in the Debian project. It's a slippery slope once you start on it.

And you keep repeating this. I am sure that Pat and team are well aware of what it takes to incorporate PAM into the system. And I'm sure they are aware of how it will act on a system.

Just let them develop the OS as they see fit. The question about PAM was already presented, and Eric even implied that it might be on the horizon ("one step at a time"). For those wanting PAM, they should take the pulseaudio addition as a sign that Pat will do what he thinks necessary, whether or not people are clamoring for it, to make sure Slackware works with its software.

Here's the opinion of someone whose opinion is influential in Slackware circles:

Given that these threads always end with people on both sides of the argument drinking too much, saying horrible things they don't really mean to each other, and then getting the party shut down by the LQ police, it seems that the best thing you can do if you want PAM considered for inclusion in Slackware is not publicly discuss the inclusion of PAM in Slackware.

"begin investigating"? LOL

Don't expect to see that in the 14.2 development cycle.

It should have bee added 4 or 5 years ago!

See one of Pat's earlier posts in the forum. Not to mention an entire thread on it, with this post from him.

Bluez does not pull in pulseaudio in Gentoo. I wonder why the dependency in Slackware?