slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages
I just thought I would post this file since I was doing it for myself. This is the stock /etc/slackpkg/blacklist file with AlienBOB's multilib and kde 4.4.2 packages added. If I screwed something up please let me know!
Code:
# This is a blacklist file. Any packages listed here won't be
# upgraded, removed, or installed by slackpkg.
#
# The correct syntax is:
#
# To blacklist the package xfree86-devel-4.3.0-i386-1 the line will be:
# xfree86-devel
#
# DON'T put any blank line(s) or any space(s) before or after the package name.
# If you do this, the blacklist will NOT work.
#
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
#
# kernel-ide
# kernel-modules
# kernel-source
# kernel-headers
# kernel-generic
# kernel-huge
#
kdelibs-experimental
#THESE ARE ALIEN BOB'S MULTILIB PACKAGES
gcc
gcc-g++
gcc-gfortran
gcc-gnat
gcc-java
gcc-objc
glibc
glibc-i18n
glibc-profile
glibc-solibs
glibc-zoneinfo
#
#THESE ARE ALIEN BOB'S KDE 4.4.2 PACKAGES
k3b
kdeaccessibility
kdeadmin
kdeartwork
kdebase
kdebase-runtime
kdebase-workspace
kdebindings
kdeedu
kdegames
kdegraphics
kdelibs
kdemultimedia
kdenetwork
kdepim
kdepim-runtime
kdepimlibs
kdeplasma-addons
kdesdk
kdetoys
kdeutils
kdewebdev
oxygen-icons
polkit-kde-1
polkit-qt-1
##THESE ARE ALIEN BOB'S KDE 4.4.2 DEPENDENCIES
ConsoleKit
PyQt
QScintilla
akonadi
attica
ebook-tools
eggdbus
hunspell
libiodbc
libmsn
libspectre
phonon
polkit
qt
shared-desktop-ontologies
sip
soprano
system-config-printer
virtuoso-ose
virtuosoconverter
#
# aaa_elflibs can't be updated.
#
aaa_elflibs
#
# Now we can blacklist whole directories
# The two versions of udev inside that dir conflicts with
# Slackware 11.0's default udev (in /slackware).
/extra/udev-alternate-versions
Big thanks to mRgOBLIN for providing me with the following command:
which if run in a directory containing packages will return an easy to copy/paste list of filenames suitable for direct copy to a blacklist file!
Alternatively you can type this inside the directory with packages:
Code:
ls -1 *.t?z | rev | cut -d- -f4- | rev
which will give you the same list but with less typing.
And since I create all my packages with the "alien" tag, this command will list all my packages you have installed (the list may be larger than just the KDE4/multilib packages):
And since I create all my packages with the "alien" tag, this command will list all my packages you have installed.
I wonder if it'd be a good idea if slackpkg or even upgradepkg itself were made tag aware and coded so that they wouldn't replace a package with one that uses a different tag (unless you tell them to). It'd certainly be useful to those of us who have a number of modified packages. Anyone have any thoughts on this?
We've mentioned it to PiterPUNK sometime ago that that would be a nice feature for slackpkg, and he agreed. Whether and when it will find a way into the program remains to be seen.
You will not see this feature added to upgradepkg ever - Slackware's pkgtools do not deal with 3rd party package tags.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.