||11-25-2012 11:46 AM
Originally Posted by vdemuth
But you have time to spend downloading compiling installing testing finding missing dependencies etc etc. Or would you prefer to be using your PC more productively?
I see this argument often and always think: "What do those people that claim to want to work more productively with their machines so that a lot of their time would be lost with installing software?" Do you really everyday install new software on your productive system?
I see normally two possibilities when it comes to production systems:
1. Either you are a user (maybe also in the admin role) of a single production system. In that case you setup the software you need exactly once, not everyday. Since you know already which software you need and which dependencies that software needs it shouldn't be as time-consuming as many people think to setup a new machine and you get the benefits from a) knowing exactly how your machine works, b) knowing exactly which software runs on your machine, and c) having the possibility to install only the optional dependencies that you need/want. This should lead in general to systems that only have needed software installed, which in turn should lead to more stability.
2. You are an admin that often has to setup a larger number of machines. In this case you still have to track down dependencies only once and testing the software is a part of your job. If compiling is a problem for you you are doing something wrong, any admin that has to do a job more than only a few times will come up with a script to do that work for him. In case of Slackware it would be nothing more than writing a few Slackbuilds, if necessary, and a queue-file for sbopkg.
Dependency tracking may make sense in case of Debian, when you have a repository with 30.000+ packages, where a large number of packages is not part of the default install. it doesn't make sense in case of Slackware, where the number of packages in the repository almost equals the number of packages that are installed in a recommended default install.
Also, many people still forget that there is no such thing like automatic dependency resolution. A package maintainer has to track down the dependencies and integrate that info into the packages. The maintainer also has to decide which optional dependencies should be compiled into the packages, which may or may not fit your needs.
I prefer to be my own package maintainer and Slackware makes it very easy to do that. Slackware is the only distro without dependency resolution (except LFS) and I am still wondering why there is such a great effort from people that are even using it to convince other users that it needs to have dependency resolution. If you want dependency resolution go for Salix, simple as that.