[SOLVED] slackpkg+ (yet another downgraded packages thread...)
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.
slackpkg+ (yet another downgraded packages thread...)
Hi everyone,
first of all I apologise for this post, as it is probably the 23rd thread regarding the topic, but after reading all the others I am still a bit unclear about what's going on.
I have Slackware64-current and my /etc/slackpkg/slackpgkplus.conf looks like this:
I have KDE 4.14.0 and KDE 5.0.1 from Alien Bob installed, plus some other packages from him, Robby and SBo. Now, I want to keep my system up-to-date with slackpkgplus, but
What I find most irritating is the proposed downgrade of kwallet. Now, I understand that slackpkg(plus) has no concept of higher or lower versions. But why then just this single one KDE packages, and not all the others, too?
Probably there's some misconfiguration of slackpkgplus on my side, but what is it?
Thanks for any help in advance!
gargamel
Last edited by gargamel; 08-29-2014 at 06:45 PM.
Reason: Corrected URLs
You *could* make your own repository of *built* SBo packages by (for example) redefining OUTPUT in sbopkg.conf and running Alien Bob's gen_repos_files.sh, and then you can use that repository in slackpkgplus.conf. There are other advanced tools that do all that.
But if you only have one Slackware box, and if you always use sbopkg to build and install, then it's easier to blacklist all SBo packages, or greylist specific SBo packages, just as you suggested.
You *could* make your own repository of *built* SBo packages by (for example) redefining OUTPUT in sbopkg.conf and running Alien Bob's gen_repos_files.sh, and then you can use that repository in slackpkgplus.conf. There are other advanced tools that do all that.
But if you only have one Slackware box, and if you always use sbopkg to build and install, then it's easier to blacklist all SBo packages, or greylist specific SBo packages, just as you suggested.
Thanks, this makes sense to me.
I consider this SOLVED now and will mark the thread accordingly. Thanks for your help to all of you!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.