Hacker News new | ask | show | jobs
by morb 3866 days ago
slackpkg doesn't do dependencies.

slapt-get (http://software.jaos.org/) does, but it needs repo that has dependency metadata. Official repos don't have it. If a repository doesn't have dependency metadata then slapt-get doesn't resolve deps for that set of packages.

Some other repos (AlienBob's for instance) do have dependency metadata, which assume that you did a full Slackware install, so only dependencies that aren't part of Slackware are listed.

There is also slapt-src (same URL) that automates installing stuff from http://slackbuilds.org/, and it resolves dependencies. It's not fullproof, but is good enough (for me, at least).

There's a new repo on http://slackonly.com/ which offers binary packages built from scripts on slackbuilds, and it looks like it has dependency metadata. I can't vouch for the quality of those packages, I haven't used it yet.

UPDATE: After skimming through PACKAGES.TXT for a few minutes, I'm not confident that slackonly repo has all dep. metadata correct, but hopefully they'll get better with it soon.

3 comments

Ah, you're right it was slapt-get that I used; it convinced me that apt-get was really good, part of the reason I moved despite up to then being more familiar with compiling my own (yay for checkinstall) or using yum.
sbotools is the magic dep mgr for slackbuilds

http://dawnrazor.net/sbotools/

slpkg is worth a look:

https://github.com/dslackw/slpkg