Sorry to quote myself but I forgot to mention one thing that I really like about Slackware packages: when you install package "foo" you have all the parts of foo. With other distributions you have foo, foo-base, foo-common, foo-dev, foo-doc, foo-libs, foo-nox, foo-gnomesupportfiles, etc.

This is often the consequence of using automatic dependencies.

*throwing that stinking rat body in this room*

How about integrating the PAM and Network Manager?

Nope. It's just about that tendencies to modularize all the things.

If you want, you can just create RPM packages without dependencies and including all files from build.

Hey there.

Using Slackware feels like using a very thought-full and intelligent piece of work all the way from the start. As all the reasons that must be put to question the so-called "modernized" have been done above and nothing remains to be said.

I have to say that being modern is being "powerful and infallible" for which Slackware is known for.

maybe you missed this

http://connie.slackware.com/~vbatts/pam/

Maybe you're looking for this thread?

IMO PAM will be in Slackware with the next big upgrade in -current. I think thats why theres virtually no advancement since 13.37 (more than 4 months).
As for networkmanager id prefer not having it but come up with a simple elegant solution regarding Slackware network rc scripts which definitely would like to see updated.
Networkmanager is horrible, id prefer to see connman in Slack. Sadly the only environment which has a GUI for it today is enlightenment.

I'm not a slackware user myself but what you are asking is kinda the equivalent of asking why a motorcycle isn't more like a car, people ride motorcycles because they like how motorcycles function, if they wanted something more like a car they'd buy a car.

Just as motorcycle riders don't want a motorcycle to become a car, slackware users like how slackware operates and asking them (slackware developers) to change slackware for your convenience would be like asking motorcycle manufacturers to make their motorcycles more car like, not gonna happen, pick a distribution that has more 'modern' features if you want them instead of trying to change slackware, otherwise make a fork of slakware that HAS the modern features you want and call it something else.

Or better yet it's like complaining a bicycle doesn't have an engine.

1 members found this post helpful.

Wtf, 3 more who voted yes?? This is not good, Pat maybe consider this now.

In fact, installpkg and slackpkg will be moved to pasture/, only to be replaced by /etc/rc.d/rc.crap-get (currently in testing/), a system maintenance daemon that automatically updates and configures your system every 30 seconds. The rc.crap-get daemon uses a PostgreSQL backend combined with systemd and Webmin to make a powerful system administration tool.

3 members found this post helpful.

Will it handle dependencies?

Hi,

I thought it was '/etc/rc.d/rc.crap -get' , '/etc/rc.d/rc.crap -new' and '/etc/rc.d/rc.crap -wipe'. I think there are several other options. Just can not get the online manuals to reveal descriptions. Think something like enema or flush.

1 members found this post helpful.

No!
There's plenty of other distros out there to pick from for those that think Slack is too much trouble.

Yes, you can. But once you start using dependencies being modular is a logical consequence. All the big distros with dependencies split their packages.

I think there is one fail safe we have to worry about with Slackware...

His Lord and Majesty The Grand High Supreme Emperor Patrick of the House of Volkerding...

...will have the final say in this, and usually as always the answer is NO.

As it is... look how long Slackware has gone without automated dependency resolution. Look at how many distributions come and go that do this only to end up forked out forgotten, and even collapse under the weight of extensive package management, and mismanagement.

Does Slackware need to end up this heavily bloated system like Ubuntu, Fedora, OpenSuSE, and others like it... HELL NO.

1 members found this post helpful.

Slackware runs fine on my rather new main computer.

I find your suggestion rather funny. You are running Arch, have not used Slackware for years and nonetheless you are making suggestions how Slackware should be. Why?
Most (if not all) Slackers are happy with Slackware the way it is. No need for automatic dependency resolution here, had that with Debian, don't want it. Also, as suggested above, if you want optimization run Slackware64 (or Gentoo).