[SOLVED] Slackpkg+ with AlienBob's KDE Packages

marnold · 09-30-2014, 09:07 AM

I've been happily using slackpkg+ to keep my Slackware64 14.1 system up-to-date and it works great. I upgraded to AlienBob's KDE 4.13.3 packages. I added kde to /etc/slackpkg/blacklist. AlienBob also updates a few default Slackware packages. That means that every time I run slackpkg upgrade-all it tells me to "upgrade" to Slackware's default akonadi, attica, libssh, partitionmanager, shared-desktop-ontologies, and soprano. Is there any downside to adding slackware64 and extra to the blacklist or will that mess some things up? Or would it be better to list those packages individually?

Alien Bob · 09-30-2014, 09:51 AM

If you are using slackpkg+ why don't you just add my KDE repository to the repository list and give my packages precedence over Slackware packages? I have been managing my own boxes like that ever since slackpkg+ was released.

Then there's no need to blacklist anything either.

Eric

bassmadrigal · 09-30-2014, 01:04 PM

I don't think adding slackware64 or extra will do anything. I think it would require an actual name within the package. If you were using regular slackpkg, you can blacklist all of Eric's packages using the following (you may also want to add [0-9]+_SBo if you use slackbuilds.org for any build scripts).

Code:

[0-9]+alien

However, as Eric mentions, you can set precedence to his packages and not run into any issues with official slackware versions overwriting his packages. I'd suggest reading his blog post on the extension as he goes in-depth explaining what it is and how to properly set it up.

http://alien.slackbook.org/blog/intr...-repositories/

EYo · 09-30-2014, 05:37 PM

Quote:

Originally Posted by bassmadrigal

I'd suggest reading his blog post on the extension as he goes in-depth explaining what it is and how to properly set it up.
http://alien.slackbook.org/blog/intr...-repositories/

Thanks for linking back to those examples. It wasn't working for me because I only listed one repo, and had kde in the blacklist file. This works, nothing blacklisted:

Code:

PKGS_PRIORITY=( ktown:.* alienbob:.* restricted:.* )
MIRRORPLUS['ktown']=http://taper.alienbase.nl/mirrors/alien-kde/14.1/latest/x86_64/
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64/
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64/

I really like slackpkg+, it's the first thing I put on a fresh install now.

marnold · 09-30-2014, 07:14 PM

Quote:

Originally Posted by Alien Bob

If you are using slackpkg+ why don't you just add my KDE repository to the repository list and give my packages precedence over Slackware packages? I have been managing my own boxes like that ever since slackpkg+ was released.

Then there's no need to blacklist anything either.

Very cool! I didn't realize that I could do that. Thanks also to EYo for the exact stuff to add to my configuration file. Very nice indeed!