LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-30-2014, 09:07 AM   #1
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 15.0 Multilib
Posts: 316

Rep: Reputation: 52
Slackpkg+ with AlienBob's KDE Packages


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?
 
Old 09-30-2014, 09:51 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113Reputation: 8113
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
 
3 members found this post helpful.
Old 09-30-2014, 01:04 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657Reputation: 6657
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/
 
2 members found this post helpful.
Old 09-30-2014, 05:37 PM   #4
EYo
Member
 
Registered: Jun 2009
Distribution: Slackware
Posts: 190

Rep: Reputation: 153Reputation: 153
Quote:
Originally Posted by bassmadrigal View Post
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.
 
2 members found this post helpful.
Old 09-30-2014, 07:14 PM   #5
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 15.0 Multilib
Posts: 316

Original Poster
Rep: Reputation: 52
Quote:
Originally Posted by Alien Bob View Post
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!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
AlienBob's Pipelight packages work for NFL Sunday Ticket too! marnold Slackware 9 11-21-2013 09:46 AM
Differences between packages of AlienBoB Repository and Slackbuilds JohnV2 Slackware 7 04-19-2012 09:53 PM
[SOLVED] Building AlienBob's KDE 4.7.2 packages from the Slackbuilds damgar Slackware 7 10-27-2011 12:11 AM
slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages damgar Slackware 7 04-08-2010 09:33 PM
Blacklist lines to keep slackpkg from overwriting Alien Bob's KDE 4.4.1 packages damgar Slackware 1 03-07-2010 12:35 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration