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.
Patiently wait for the release of Slackware 14.2 then the updates of the SlackBuilds @ slackbuilds.org for 14.2, then upgrade sbopkg, configure it, sync the repository, use sqg to write a queue file for virt-manager then use it to build and install virt-manager.
Until then and as far as I am in concern, you are on your own.
Last edited by Didier Spaier; 04-23-2016 at 04:37 AM.
Thanks Ponce I was missing python-requests as you observed. I was using the correct repository. For some reason the python-requests never showed up as a prereq for anything else. I usually work backwards from what I want to build on SlackBuilds but for some reason python-requests never was listed as a requirement (or I missed it). Should have checked my build list from before to see if it was there.
It's seems to work now.
I thought I was missing something, just not sure what.
Thanks willysr I don't use sqg but I guess it's probably time to start. Must have missed python-requests. I will try to pay better attention in the future.
to find that requires. It does not show up in the readme with sbopkg looks like it may be cutoff oh well I got worked out and learned several things thanks for the help.
if you haven't done it already you can download a local copy cloning the git repository (I linked above in my previous post another one where I explain how to do it) so it could be easier parsing it.
the *.info files show mandatory dependencies for the relative SlackBuild (the REQUIRES variable), while in the READMEs are listed the optional ones.
OK that sounds good. Just to make sure though this only involves the requirements and not necessarily the optional things that might be required for whatever it is you want to do.
I need OpenShot but that has lots of optional things that I want to use so in that case I need to do some manual builds to get what I want ?
Sorry for the delay. But it really depends on how the package maintainer and the program itself are set up. Most ./configures will autodetect software, so if you have it installed, it will add support for it. Some, like ffmpeg, require you to manually enable options within the configure line.
If the program is set to autodetect optional dependencies, the package maintainer doesn't have to do much other than notify you what the optional dependencies are. You can then ensure they're installed before you install the main program and then all the support will be there. If it is something that requires you to manually specify the options, the package maintainers will usually put checks within the SlackBuild for a certain variable, so with ffmpeg, you could end up with a long line of variables like
The latter setups are more difficult to use with tools like sbopkg, so, for me, I'll usually edit the SlackBuild and remove the if/then checks for the variables I desire. I suppose you could also add the variables at the top of the SlackBuild.
For the simpler autodetect configures, as long as you have the optional software installed beforehand, that's all you need to do. If I want to fully automate the building, I'll usually edit the requires line on the .info to change it to contain what I want built. A good example of this for me is kodi. It used to be that libmicrohttpd was an optional dependency. I wanted it to be built automatically with kodi. I also didn't want it to build jdk because 1. it wouldn't work unless I already downloaded the source, and 2. I used Eric's precompiled openjdk. So on the kodi.info REQUIRES line, I removed jdk and added libmicrohttpd and regenerated the queue file with sqg. Then I removed the if/then check in the SlackBuild to see if I specified that WEBSERVER=yes and had it set the needed variable to enable it during the compilation.
This is falls under a bit of the advanced usage of sbopkg. For others, it might be easier to just download those crazy builds manually and run them manually from the CLI.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.