Merge server and local lists in subshell. Filter once.
This takes the server and local package lists, sorts, applies blacklist,
sorts again to make a large list of package names in blacklist.
Use internal printf rather than external ls to build local list.
Also pass local package list to blacklist
This creates a blacklist of package names from regexp in original
file (/etc/slackpkg/blacklist) and uses the precreated list for
later comparison
Signed-off-by: Robby Workman <rworkman@slackware.com>
As of slackpkg shipped with Slackware 15.0, it is no longer
supported to add packages to /etc/slackpkg/blacklist using
the slackpkg executable; this should only be done with an
editor pointing at /etc/slackpkg/blacklist
* Modify checkchangelog() function to only check CHECKSUMS.md5.asc.
* Remove unneeded check of ChangeLog.txt from checkchangelog() function.
* Move fetching of ChangeLog.txt to updatefilelists() function.
* Modify check-updates to output need to update to stderr so cron
jobs will notify sysadmin.
Signed-off-by: Robby Workman <rworkman@slackware.com>
This reverts commit fcc58ff506
because it breaks lxc container creation; ponce stated on LQ
that "seems that forcing $CONF under $ROOT is what break things
here: $CONF in the template is used to have a temporary location,
outside of the container, in which to store the template, a
blacklist and a mirror configuration for the container creation"
This adds ./$PKGMAIN/ to a blacklisted set line, which
ought to say turn kde/ into ./slackware64/kde as it listed in the
temp pkglist. I've tightened up the patches/pasture/extra etc. lines
too.
Signed-off-by: Robby Workman <rworkman@slackware.com>
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>
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>
This should never be an issue on a properly installed
system (assuming slackpkg is installed on the system),
but it doesn't hurt anything either to be safe.
