Blacklisting gcc when using alien multilib
by djringjr from LinuxQuestions.org on (#52Z76)
I followed the instructions on page https://docs.slackware.com/slackware:multilib
I like to use spi to update and upgrade because it seems easier.
But I became cautions because it seemed to say it wanted to upgrade my gcc.
Then I used slackpkg after updating and used command slackpkg search gcc.
Code:# slackpkg search gcc
Looking for gcc in package list. Please wait... DONE
The list below shows all packages with name matching "gcc".
[ upgrade ] - gcc-5.5.0_multilib-x86_64-1alien --> gcc-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-g++-5.5.0_multilib-x86_64-1alien --> gcc-g++-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-gfortran-5.5.0_multilib-x86_64-1alien --> gcc-gfortran-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-gnat-5.5.0_multilib-x86_64-1alien --> gcc-gnat-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-go-5.5.0_multilib-x86_64-1alien --> gcc-go-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-java-5.5.0_multilib-x86_64-1alien --> gcc-java-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-objc-5.5.0_multilib-x86_64-1alien --> gcc-objc-5.5.0-x86_64-1_slack14.2
[ installed ] - gccmakedep-1.0.3-noarch-1
So it looks like if I use slackpkg or spi to upgrade I will be replacing multlib gcc with regular gcc despite my haing done this step:
Code:If you use a package manager like slackpkg on Slackware releases older dan 13.37 you will have to add all the glibc and gcc package names to its package blacklist. If you do not take this precaution, you run the risk of your package manager accidentally replacing your multilib versions with Slackware's original pure 64-bit versions!
If you run Slackware 13.37 or newer, then slackpkg supports regular expressions in the blacklist file. In that case, a single line in /etc/slackpkg/blacklist will be enough to blacklist all of my packages (including multilib gcc and glibc packages and all compat32 packages):
[0-9]+alien
[0-9]+compat32
On the other hand, if you are using the slackpkg extension called slackpkg+ then you should definitely not blacklist these packages, because that prevents slackpkg+ from managing them!That says if I use that code, it will blacklist the multilib packages from alien, but that's not what I want to do, it's in a section on that page telling how NOT to overwrite the multilib packages from alien.
Either I am confused on that page should be edited as the guidance it offers is not the guidance that is needed.
Here's what I put in my /etc/slackpkg/blacklist file:
Code:# 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]+alien
[0-9]+compat32Did I misunderstand what is on, https://docs.slackware.com/slackware:multilib?
Thank you,
djringjr


I like to use spi to update and upgrade because it seems easier.
But I became cautions because it seemed to say it wanted to upgrade my gcc.
Then I used slackpkg after updating and used command slackpkg search gcc.
Code:# slackpkg search gcc
Looking for gcc in package list. Please wait... DONE
The list below shows all packages with name matching "gcc".
[ upgrade ] - gcc-5.5.0_multilib-x86_64-1alien --> gcc-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-g++-5.5.0_multilib-x86_64-1alien --> gcc-g++-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-gfortran-5.5.0_multilib-x86_64-1alien --> gcc-gfortran-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-gnat-5.5.0_multilib-x86_64-1alien --> gcc-gnat-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-go-5.5.0_multilib-x86_64-1alien --> gcc-go-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-java-5.5.0_multilib-x86_64-1alien --> gcc-java-5.5.0-x86_64-1_slack14.2
[ upgrade ] - gcc-objc-5.5.0_multilib-x86_64-1alien --> gcc-objc-5.5.0-x86_64-1_slack14.2
[ installed ] - gccmakedep-1.0.3-noarch-1
So it looks like if I use slackpkg or spi to upgrade I will be replacing multlib gcc with regular gcc despite my haing done this step:
Code:If you use a package manager like slackpkg on Slackware releases older dan 13.37 you will have to add all the glibc and gcc package names to its package blacklist. If you do not take this precaution, you run the risk of your package manager accidentally replacing your multilib versions with Slackware's original pure 64-bit versions!
If you run Slackware 13.37 or newer, then slackpkg supports regular expressions in the blacklist file. In that case, a single line in /etc/slackpkg/blacklist will be enough to blacklist all of my packages (including multilib gcc and glibc packages and all compat32 packages):
[0-9]+alien
[0-9]+compat32
On the other hand, if you are using the slackpkg extension called slackpkg+ then you should definitely not blacklist these packages, because that prevents slackpkg+ from managing them!That says if I use that code, it will blacklist the multilib packages from alien, but that's not what I want to do, it's in a section on that page telling how NOT to overwrite the multilib packages from alien.
Either I am confused on that page should be edited as the guidance it offers is not the guidance that is needed.
Here's what I put in my /etc/slackpkg/blacklist file:
Code:# 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]+alien
[0-9]+compat32Did I misunderstand what is on, https://docs.slackware.com/slackware:multilib?
Thank you,
djringjr