Quote:
Originally Posted by nooralain
know much about these packaging stuff
|
'Packages' is just jargon for linux programs. Something i forgot to mention in my previous post is that Slackware comes with a lot of software and most other things are usually very easy to get hold of, thanks to the great community. Debian and other boast they've some huge amount of packages, but the reality is that most users will only use a small amount of programs and once you've them installed, why does dependency checking matter. And another side note. Slackbuild.org, which is one of the main Slackware resources for getting third party packages; for every package, it tells you very clearly what dependencies aren't fulfilled on a default Slackware install, and all of those dependencies are are easily obtainable.
If you want to learn a little bit about Slackware, i highly recommend The podcast 'Linux Reality' the 'special episode one, slackware'. It is old, i think about five years and the host Chess Griffin is referring to version 12.1 i think, but 99% of the information is still relevant today. Speaking of that, that's another good thing about Slack, very little changes as time goes on, it just remains the rock that it is.