>Frustration Free Packaging >If you’ve heard anything bad about Slackware, it’s almost certainly been about the software packages. Or more specifically, the la

>Frustration Free Packaging >If you’ve heard anything bad about Slackware, it’s almost certainly been about the software packages. Or more specifically, the lack of intelligent dependency management. In other distributions, the package manager understands what software each package relies on to function, and will prompt you to install them as well to make sure everything works as expected. There is no such system in Slackware, but that is also by design. >In an effort to make things as simple as possible, the expectation is that you install everything. Slackware is developed and tested with the assumption that you have a full installation of every package in the repository. In fact, this is the default mode for the Slackware installer; you have to switch into “Expert” mode if you don’t want everything. >If you don’t want a full install and would rather pick and chose packages, you are free to do so, but you’ll need to manually handle dependencies. If you get an error about a missing library when you try to start a program, it’s up to you to find out what it depends on and install it. You’ll quickly develop a feel for just what is and isn’t required in a Linux system by going through and manually solving your own dependencies, which again comes in handy if you are trying to tailor-fit an OS to your specific requirements. I realise this is worded pretty unambiguously, but can somebody confirm this means what it in fact seems to mean? I find that extraordinary, and though having heard mention of Slackware's packaging system before, I never heard this detail about every package being installed. How does that even work? The repositories must be tiny?!