In RTFM I understand (to be corrected) that Slackware includes the dependencies for building packages from source. But since I prefer to get binaries (having been a Windows user for way too long and grown accustom to that method) and becuase my machine is light on resource power, I have a question about dependencies for packages and the other package install tools.

In the following thread: http://www.linuxquestions.org/questi...es-4175493466/
there was discussion of package dependencies for slackware builds being included with a full install. I'm a little confused and have always followed the slackpkg usage instructions and checked the package "README" and "REQUIRES" before any new package install. Am I being redundant to check the REQUIRES statement, because for all slackpkg packages the requirements are already present as a result of the full Slackware 14.1 install? I've installed slackpkg+, for multilib, aliendbob, salixos, slacky, e17, would I need to check those REQUIRES if not for slackpkg?

Also if I don't find a package I'm looking for with slackpkg, then I usually move on to sbopkg. Again, following instructions I check the README and REQUIRES statements before adding to queue and installing. Obviously checking all the REQUIRES means a second terminal open and then "whereis foo.exe" or "locate foo.exe". Again am I wasting time and being redundant?

I don't often simply pull down a package from the net and installpkg, but should I be doing that before slackpkg and sbopkg?
I think the only time I did was a ftp from OSUOSL.org Slackware support, so figured all the depend's were accounted for. Was that right?

OR was the article simply not being accurate?
Thanks for advice to a newbie who is still working out the Slackware logic.

slackpkg does no dependency resolution, so for packages from third party repositories, like that from AlienBob or Salix you will still have to check if you need to install additional packages (which are usually offered by the same repository). The same is true for building packages using scripts from SlackBuilds.org, you will have to build dependencies first, before installing the package you want to install. Usually dependencies that are already installed by a full Slackware installation are not listed in third party repos/at SBo.

slackpkg can only be used to manage official repositories, unless you installed slackpkg+
sbopkg is used to manage SBo repositories, and if you combine it with sqg (available since 0.37), you can generate all queues file which can be used to resolve dependencies for all packages in SBo repository

Thank you TobiSGD, I wasn't sure if the required dependencies would be listed, so your reply confirms that if the full install was done, those packages/apps won't be listed in the slackpkg OFFICIAL repository, but other repositories I'll have to continue to check the README and REQUIRES. I often find when using SBopkg that the REQUIRED pkgs are already installed, and they are also listed as REQUIRES: SO as the Slackbook says, read the documentation before installing any packages.
I guess the only question unanswered is if the OFFICIAL packages from OSUOSL.org for installpkg also may have dependencies not already installed with a full install?

Since slackware assume that you do a full install, all the dependencies needed are already included in Slackware's DVD / repository, unless you install a third party apps/libraries

SBo's REQUIRED line only list dependencies found on SBo repositories, not in Slackware's.

oops wrong thread

Thank you WillySr, To clarify I did install slackpkg+ and have additional repositories from AlienBob, SalixOS, and e17. I also just found the instructions for using sqg and will use that on a package by package approach going forward, rather than building the queue by hand in sbopkg. It should cut down on the time needed to assemble a package like ClamTK.