LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-27-2016, 10:09 PM   #1
offgridguy
Senior Member
 
Registered: Nov 2015
Location: Alberta Canada
Distribution: Windows10, Debian
Posts: 1,109

Rep: Reputation: 147Reputation: 147
Blacklist question


Thanks to a lot of help from forum members, I am learning how to install third party software. I understand I have to blacklist these packages to keep slackpkg from uninstalling them whenever I upgrade the packages.
I read the slack docs regarding this and I edited the /etc/slackpkg/blacklist file.

It now appears as this.

Quote:
# You can blacklist using regular expressions.
#
# Don't use *full* regex here, because all of the following
# will be checked for the regex: series, name, version, arch,
# build and fullname.
#
# This one will blacklist all SBo packages:
#[0-9]+_SBo
[0-9]+_SBo
[0-9]+alien

root@darkstar:/etc/slackpkg#
Is this correct? Or is there more too this?
 
Old 09-28-2016, 12:08 AM   #2
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 471
Blog Entries: 2

Rep: Reputation: 291Reputation: 291Reputation: 291
Quote:
Originally Posted by offgridguy View Post
Thanks to a lot of help from forum members, I am learning how to install third party software. I understand I have to blacklist these packages to keep slackpkg from uninstalling them whenever I upgrade the packages.
I read the slack docs regarding this and I edited the /etc/slackpkg/blacklist file.

It now appears as this.



Is this correct? Or is there more too this?
That looks good, you could also blacklist individual packages by putting down their name.
 
1 members found this post helpful.
Old 09-28-2016, 09:40 AM   #3
offgridguy
Senior Member
 
Registered: Nov 2015
Location: Alberta Canada
Distribution: Windows10, Debian
Posts: 1,109

Original Poster
Rep: Reputation: 147Reputation: 147
Thank you.
Since the SBo command uses an underscore and the alien command does not.
If I were blacklisting an individual package, would it be
[0-9]+<package name> or
[0-9]+_<package name>

Last edited by offgridguy; 09-28-2016 at 09:52 AM.
 
Old 09-28-2016, 10:27 AM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,314

Rep: Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019Reputation: 5019
Quote:
Originally Posted by offgridguy View Post
Thank you.
Since the SBo command uses an underscore and the alien command does not.
If I were blacklisting an individual package, would it be
[0-9]+<package name> or
[0-9]+_<package name>
Actually, neither. For a single package, you would just put the package name, and that's it. The SBo vs alien is how they format their package names. The 0-9 portion is for the build number at the end of the package, then SBo adds an "_SBo" at the end of that, where Eric just adds "alien". See the package names below for examples.

Code:
wine-1.9.15-x86_64-1alien.txz
wine-1.9.15-x86_64-1_SBo.tgz
If you wanted to just blacklist wine, you would just need to put wine.
 
3 members found this post helpful.
Old 09-28-2016, 10:44 AM   #5
offgridguy
Senior Member
 
Registered: Nov 2015
Location: Alberta Canada
Distribution: Windows10, Debian
Posts: 1,109

Original Poster
Rep: Reputation: 147Reputation: 147
Thank you, that helps.
I am just wondering, does slackpkg+ need to be blacklisted?
 
Old 09-28-2016, 11:18 AM   #6
Slax-Dude
Member
 
Registered: Mar 2006
Location: Valadares, Portugal
Distribution: Slackware
Posts: 451

Rep: Reputation: 208Reputation: 208Reputation: 208
Quote:
Originally Posted by offgridguy View Post
I am just wondering, does slackpkg+ need to be blacklisted?
If you use slackpkg+ you should not need blacklists at all, if the packages that don't come from third party repositories come from your own local repository.

In other words: you can let slackpkg+ handle the local dir, where you store the packages you compile on your box, as a local repository.
Then you just give it a higher priority over the other repositories and you will never have a locally compiled package (or alienbob's or SBo's) replaced by a stock slackware one that might be of an older version.
 
1 members found this post helpful.
Old 09-28-2016, 11:24 AM   #7
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 963

Rep: Reputation: 902Reputation: 902Reputation: 902Reputation: 902Reputation: 902Reputation: 902Reputation: 902Reputation: 902
Quote:
Originally Posted by offgridguy View Post
Thank you, that helps.
I am just wondering, does slackpkg+ need to be blacklisted?
Unless you want to prevent a package to be updated, there's no reason to put it on blacklist.

On the other hand, with slackpkg+, if you want a package P from repository R and there's another version of P in repository R' that you don't want, you have three choice :
  1. give priority to all packages from R, then R'

    To do that, edit /etc/slackpkg/slackpkgplus.conf. Ensure that PKGS_PRIORITY is uncomented, and add the priorities you want.

    For instance, if you only want to give priority to all packages from restricted then alienbob you can set PKGS_PRIORTY as below :
    Code:
    PKGS_PRIORTY=(restricted alienbob)
  2. give priority to package P from repository R only

    The same as (1), excepted than instead of giving priority to all packages from a repository, you give priority to a specific package.

    For instance, to give priority to ffmpeg from restricted repository, and then, to all packages from alienbob, you'll set PKGS_PRIORITY as below :

    Code:
    PKGS_PRIORITY=(restricted:ffmpeg alienbob)
  3. blacklist R':P

    currently, slackpkg+ does not support syntax repository:name in blacklist (but this could change soon). However, it can be done using the (undocumented) syntax below :

    Code:
    SLACKPKGPLUS_<repository-name> <pattern>
    For instance, if you want to blacklist package ffmpeg from slacky, add the regexp below in the blacklist :

    Code:
    SLACKPKGPLUS_slacky ffmpeg
    Quote:

    Attention, that kind of rule does not work as it should with repositories (like alienbob and restricted) whose packages have the same version and build number.

Hope this help.

-- SeB

Last edited by phenixia2003; 09-28-2016 at 01:40 PM.
 
Old 09-28-2016, 03:34 PM   #8
offgridguy
Senior Member
 
Registered: Nov 2015
Location: Alberta Canada
Distribution: Windows10, Debian
Posts: 1,109

Original Poster
Rep: Reputation: 147Reputation: 147
Thank you all for the response, this is very helpful.
 
  


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
[SOLVED] slackpkg blacklist question Woodsman Slackware 3 10-23-2013 04:37 PM
[SOLVED] Question about modprobe and blacklist flyinggeorge Linux - Newbie 10 07-14-2013 05:20 PM
blacklist pagedown1 Linux - Newbie 1 02-02-2011 04:09 PM
[SOLVED] Newbie SPAM Email blacklist question AndeAnderson Linux - Server 9 01-22-2010 11:32 AM
?Odd bug. modprobe.blacklist~ behaves as modprobe.blacklist arubin Slackware 1 11-05-2006 07:08 PM

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

All times are GMT -5. The time now is 08:38 AM.

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