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.
can there be an option to ignore dependency mismatches. the build for vlc requires live555 and the live555 build is broken because the src file doesn't exist anymore. I edited the build version to match the newer file, but when I try to install vlc from slpkg it still fails on live555.
Just to elaborate a little, what I was thinking was that there could be a switch that tells the program to skip over broken dependencies. Kind of like the --skip-broken switch in yum, except obviously with slpkg you can't go on and compile until the dependencies are resolved. This way you can get all the working dependencies installed and go back to take care of the broken ones by hand. Then you could have another switch that tells the program to ignore the dependency mismatches and try to compile the package.
Thank you for the nice ideas !!!
Nice sounds and the choice --skip
Now working to create a blacklist configuration file in the directory /etc/slpkg in which there will be the file blacklist.
Just to elaborate a little, what I was thinking was that there could be a switch that tells the program to skip over broken dependencies. Kind of like the --skip-broken switch in yum, except obviously with slpkg you can't go on and compile until the dependencies are resolved. This way you can get all the working dependencies installed and go back to take care of the broken ones by hand. Then you could have another switch that tells the program to ignore the dependency mismatches and try to compile the package.
I downloaded and installed slpkg earlier this week. Everything went smooth with my slackware64 14.1
Pulled a few builds off SlackBuilds.org and installed them just to check it out. Everything worked.
I think its great. Especially for newer UN*X users.
I recently installed Slackware64 alongside Windows 7 for a friend of mine. New to UN*X.
This tool helps him alot too.
Thanks for all your work
I would like to know what can this tool do that slackpkg+ by zerouno can't do ?
Seems like overlapping tools to me.
This tool is more like a sbopkg + dependency resolution + slackpkg+. slpkg is able to actually compile stuff automatically from slackbuilds.org and is able to resolve dependencies. slackpkg+ just installs already compiled packages that are present on some repository.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
