This should fix blacklisting of entire package sets; thanks much
to David Woodfall (dive) for this. Note that the sample blacklist
file has changed to reflect the new syntax for blacklisting sets
(add a trailing slash, e.g. "kde/")
- Allow blacklisting of individual packages without collateral
damage (e.g. glibc ---> glibc-*). This changes the prior behavior
of the blacklist function; previously, adding "glibc" to the
blacklist would cause glibc, glibc-profile, glibc-zoneinfo, et al
to be ignored by slackpkg. The new behavior is that *only* the
glibc package is ignored. If you want to blacklist all packages
whose names begin with glibc, you would need to add "glibc.*" to
the blacklist now. Also note that any special characters, e.g. "+",
will need to be escaped in the blacklist file. (David Woodfall)
- Add support for listing .new files without PAGER (David Woodfall)
- Remove switch.ch mirrors
- Add config option to allow *not* saving .orig configs (Darren Austin)
- Mention possible stale mirror if CHECKSUMS.md5 gpg verify fails
- Clarify that a press of "Enter" is needed to confirm kernel change
(Mario Preksavec)
- doinst.sh Don't remove ChangeLog.txt upon upgrade/reinstall.
(Patrick Volkerding)
- mirrors-x86*.sample: Remove bjtu.edu.cn mirror
- Fix for /var/log/packages/ possibly being a symlink to elsewhere
- Use CHECKSUMS.md5.asc to determine ChangeLog newness
(Patrick Volkerding)
In short, it seems impossible to blacklist some packages without
catching other undesirable packages. As an example, blacklisting
glibc will also catch glibc-zoneinfo (and the other glibc-*)
packages. It would be good to have the ability to blacklist only
the glibc package without it catching the others.
With this change, if sysadmin wants the blacklist to be "greedy,"
then adding "glibc.*" to the blacklist will do that.
Reported-by: Peter Hyman <pete@peterhyman.com>
Signed-off-by: Robby Workman <rworkman@slackware.com>
