coroner wrote:Salix is not equal to a full installation of slackware linux. You'll have to install the missing packages from salix/slackware repository.
p.s. SBo repository is not part of this project. If you want to put the program dependencies from the * .info file, use a third-party tools. For example slpkg.
Of course I installed those missing dependencies, but I think you are missing a point here. SBo repository is not part of Salix, BUT there is a local copy in Salix repos, where missing dependencies are addressed. This is explained
here:
laprjns wrote:Also since all slackbuilds scrips assume a complete Slackware installation, once in a while you will come across a script that will fail due to a missing dependencies (usually a build time dependency). In this case Salix can and does fix this, by having a list of additional dependency is the Salix Salckbuild mirror repository. Here's some info on the Salix SBo repo.
http://salixos.blogspot.com/
and explained in more detail in the blogspot link above (together with other useful information):
we have a mechanism for adding "missing" dependencies in our copy of the SBo repository. For example, the ardour SlackBuild requires cmake to build. Now, cmake is always thought to be present in a Slackware installation, otherwise it is not a full Slackware installation and it is not supported in any way. In Salix though, cmake is definitely not part of a standard installation and so we add it as an extra dependency for ardour.
......
With SBo being a moving target though, this process will always be ongoing and will never be 100% complete. If you find a SlackBuild that is missing some dependency, please report it, either in our mailing list or in our forums.
and that's what I did, reported two missing dependencies for the package hugin. Now, I suspect the mechanism of adding missing dependencies mentioned above is actually the file
SBoADD, where a missing dependence (cmake) for hugin is already present, while it is not mentioned in the corresponding
Sbo's info file. My guess is the additional dependencies in SBoADD are processed by gslapt/slapt-get. That way, SBo's missing dependencies are fixed, while the Salix copy of SBo is essentially intact, and updated when the original SBo does. If I am correct, Salix's way to fix SBo's missing dependencies is simple and clever, perfectly matching the "KISS" principle.
