Fix support for blacklisting entire package sets

Blacklisted sets now need a trailing / (eg. kde/)

Anything with a trailing slash is excluded from having \s added to it.
Then the slash is removed so the set is picked up by the old
functionality.

Signed-off-by: Robby Workman <rworkman@slackware.com>

1 files changed, 9 insertions, 5 deletions

diff --git a/files/blacklist.new b/files/blacklist.new
index df47915..34cf0d1 100644
--- a/files/blacklist.new
+++ b/files/blacklist.new
@@ -7,9 +7,11 @@
 #
 # 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.
+# Don't use *full* regex here, because all of the following will be checked 
+# for the regex: series, name, version, arch, build, and fullname.
+# When blacklisting packages, you can use extended regex on package names
+# (such as xorg-.* instead of xorg-server, xorg-docs, etc), and a trailing 
+# slash for package series ("n/", "ap/", "xap/", etc).
 #
 # To blacklist *only* the "xorg-server" package, use this:
 # xorg-server
@@ -17,12 +19,14 @@
 # To blacklist *all* of the "xorg-server-*" packages, use this:
 # xorg-server.*
 #
+# To blacklist the entire KDE package set, use this:
+# kde/
+#
 # You will need to escape any special characters that are present in the
 # package name. For example, to blacklist the gcc-g++ package, use this:
 # gcc-g\+\+
 #
-# DON'T put any space(s) before or after the package name or regexp.
-# If you do this, the blacklist will NOT work.
+# DON'T put any space(s) before or after the package name or regex.
 #
 # Automated upgrade of kernel packages may not be wanted in some situations;
 # uncomment the lines below if that fits your circumstances: