SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The SlackBuild files are just scripts. Most of the time, it's the configure script (that comes with the program you want to build, but not the SlackBuild) that checks for certain dependencies on the system.
Do you mean building packages without the required dependencies? I guess this is not possible by definition, and if you find out a way you'll end up with a broken package.
Last edited by Philip Lacroix; 05-26-2013 at 02:10 AM.
As far as I understand it, the slackbuild dependencies are advisory. I think you can go ahead and build. Of course, the build will fail if the required libraries are not there, but you may be lucky. (I doubt it tho').
You usually don't; the reason they are called dependencies is because the program depends upon them to build/work.
There are times where there are optional dependencies, in which case leaving them out just means missing out on an optional feature, but cases like that are typically clearly laid out on the documentation supplied with the slackbuild.
Actually i tried to install the jack-audio-connection-kit package using the
installpkg and got some dependencies requirement message.
And when tried to install this package "libgnomecanvasmm" (not sure i spelt correctly) and got the error "No package: gtkmm-2.4" and "No package libgnomecanvas". And it also mentioned of the "pkg-config" which
suppose to be inside the file "SlackBuild" comes with the package to be installed. (i didn't write down the exact error message at that point of time.)
It seems to me that "pkg-config" could control whether or not to install
the dependencies.
If you want to avoid issues, do a full installation. If you do, you'll never see "missing requirements" messages while running programs included in the installation dvd.
If you install from SlackBuilds, you need to understand the following: A SlackBuild is a script that controls how to build a single package. It does not resolve dependencies or have any dependency check inside.
The build process checks for required libraries, but it does so via the build scripts included in the source package. This is: each source package knows how to build itself, and includes code to check for required and optional dependencies. All that a SlackBuild does is to run the appropriate commands to launch the build process as defined by the package creator, and then create an installable package from what was compiled.
Slackware package management does not resolve dependencies, nor it enforces them. You must to build or install required dependencies, and you build or install optional dependencies if you want to get additional functionality.
Note that, in most cases, the description of the packages at slackbuilds.org assume that you have performed a full installation, so not all dependencies are listed, only those not included with the Slackware distribution.
To avoid issues and manual work, use sbopkg with the queue files from http://gitorious.org/sbopkg-slackware-queues
That is the best way to make sure all dependencies are compiled when you try to build something from slackbuilds.org
This reminded me to do something I've been meaning to do for awhile: upload a copy of the 'sqg' sbopkg queuefile generator script along with a full set of updated queuefiles. You can grab this at: https://github.com/chessgriffin/sqg
I just built the jack-audio-connection-kit package from slackbuilds.org on a Slackware64 14.0 system that was recently built via a full install. I don't have libgnomecanvasmm or gtkmm, etc., installed on my system, and the jack-audio-connection-kit build didn't require them. Perhap's in the OP's case, there are some conditional dependencies being pulled in based on what is already installed on his system.
I don't have libgnomecanvasmm or gtkmm, etc., installed on my system, and the jack-audio-connection-kit build didn't require them. Perhap's in the OP's case, there are some conditional dependencies being pulled in based on what is already installed on his system.
The OP is probably installing something else (like Ardour) that requires both jack and libgnomecanvasmm.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.