2 ms·
As far as I read about it, they don't! Dependency resolution is fully up to the user. > The package management system does not track or manage dependencies; ho
by Gentil 5y ago
As far as I read about it, they don't! Dependency resolution is fully up to the user.
> The package management system does not track or manage dependencies; however, when performing the recommended full install, all dependencies of the stock packages are met. For custom installations or 3rd-party packages, Slackware relies on the user to ensure that the system has all the supporting system libraries and programs required by the program. Since no official lists of dependencies for stock packages are provided, if users decide to install a custom installation or install 3rd-party software, they will need to work through any possible missing dependencies themselves. Since the package manager doesn't manage dependencies, it will install any and all packages, whether or not dependencies are met. A user may find out that dependencies are missing only when attempting to use the software.
Source - https://en.wikipedia.org/wiki/Slackware#Dependency_resolution https://en.wikipedia.org/wiki/Slackware#Dependency_resolutio...
- na85 5y agoOof, that sounds like a lot of work. Simplicity is a virtue but sometimes the juice isn't worth the squeeze.
- Gentil 5y agoYes. I think the question always is where should I stop?. Cos it is a tool to get things done right? While I think it is difficult to get Arcg going, the whole point of that effort is that I don't have to deal with it much after that. It is a rolling release and get the latest upstream releases which is not meddled with by distro much. Unless you are meddling with it too much, it is very stable IMO.