Thanks for the update.
@tuxdev : I'll give that a whirl in a vm and see.
@rworkman : get back to work!
I've been toying with this in my head as well for the past few days.
For sake of simplicity (or what works in my head
) Yes, I know this is very 'debianista'
but hear me out on this one
The stock blacklist file is comprised of three sections:
So what if the blacklist file was changed to be four files:
4. blacklist.variables (this would be a file, where the admin would simply put in his/her/it's desired buzzwords, wildcards, such as "OLDFOGIE" or "SBo" or "rlw" or "alien".
Then slackpkg would simply have to "source" the four text files (blacklist.kernels , blacklist.packages, blacklist.folders, and blacklist.variables)
Then when 'slackpkg update' is called, it would run a simple "ls /var/log/packages |grep OLDFOGIE" (and whatever else is in blacklist.variables) and put that into blacklist.packages file. So the blacklist.packages file is always updated to reflect the present state of the custom user installed packages, eg the "OLDFOGIE", etc.
Just a thought, whew too much thinking.