This is an old revision of the document!
Table of Contents
Slackware
Related projects
What I don't like
Headline ``What I hate about/in Slackware'' would be more appropriate. I've decided to put down this list with which feel free to disagree.
- messy and non-portable shell scripts that come with/are core of Slackware - RC scripts, installpkg, …
- network RC script that's way old for today - yeah, other distributions got it right
- slackpkg - what a terrible tool and your doom
- suggested package dependencies
Let's talk about dependencies a bit more, because no package dependencies is Slackware's feature and policy. And it would be all great and cool only if things didn't get more and more complicated over the time - new libraries added, new software added, package count doubled in 11 years(actually it was in one year between versions 11.0 and 12.0), 100 new packages added in ~ 2 years. Anyway, how long is this manageable? Or do you have everything, every single package that comes from “official” tree, installed? Really? I don't believe it.
I'm not saying Slackware should get package dependency like, eg. RPM based distributions have, but it should get “suggested” dependency. In other words suggest what packages might be required in order to get some application running.