SpelledJ |
05-24-2010 10:29 PM |
Quote:
Originally Posted by foodown
(Post 3978822)
I mean, maybe my experience is not common, but reviewers who say, "Slackware requires a lot of work after the installation to make it a modern desktop" don't make any sense to me. Slackware 13, at least, and 12 as well from what I remember, is working right out of the box . . . X, mouse, sound, touchpad, webcam, video acceleration . . . what exactly are these people having to do?
|
To answer Damgar's question, no, I don't really think the quote in his original post is entirely fair to Slackware. My initial impression is that the reviewer is implying that Slackware is unusable as a vanilla distro, and that it must be converted into some derivative distro like Vector or Zenwalk before it's a complete system.
I will give them the benefit of the doubt when comparing repositories of offical packages, though. Do a full install of Slackware and you still have a fairly basic Unix workstation setup. Its installed packages are weighed more toward software development and network administration than typical consumer multimedia applications, like ripping CDs to MP3, playing or ripping DVDs, connecting to digital cameras, etc.
Say you want a video editing workstation. Starting with Slackware will require a significantly larger amount of work to get something like KDEnlive working than a distro like Debian or Kubuntu. I agree with you, foodown, but the features you describe as the basis of a modern desktop may be a lot smaller list than some reviewers have in mind.
If someone wants a long list of multimedia capabilities, Slackware can create dependency Hell pretty quickly. That's where a dependency-checking packaging system becomes a nice feature of a distro. Even with slackbuilds.org you're going to be doing more work tracking down dependencies than you would using synaptic. See Woodsman's essay here for an overview of the additional packages needed to activate all of the back end capabilities of K3B, for example.
|