LinuxQuestions.org - [SOLVED] Blacklist question

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Blacklist question (https://www.linuxquestions.org/questions/slackware-14/blacklist-question-4175590289/)

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?

Quote:

Originally Posted by offgridguy (Post 5610792)

That looks good, you could also blacklist individual packages by putting down their name.

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>

Quote:

Originally Posted by offgridguy (Post 5610961)

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.

Thank you, that helps.
I am just wondering, does slackpkg+ need to be blacklisted?

Quote:

Originally Posted by offgridguy (Post 5610985)

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.

Quote:

Originally Posted by offgridguy (Post 5610985)

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 :

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)
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)
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

Thank you all for the response, this is very helpful.