slackpkg blacklisting ; can a wildcard be used?

Old_Fogie · 12-15-2009, 11:55 AM

Hello all,

Sorry if I've missed this in the doc's, but I don't see the ability to "wildcard" blacklist for packages to _not_ be changed out via the slackpkg program.

More specifically, I tagged all my packages like this:

mozilla-firefox-3.6b4-i486-1_OLDFOGIE.tgz

note the "OLDFOGIE" in my package name?

So can something such as:

Quote:

*OLDFOGIE*

be put into slackpkg blacklist file?

Thank you in advance.

-Fogie.

Didier Spaier · 12-15-2009, 02:58 PM

Just tried (glibc* and gcc*), doesn't work.

So either blacklist individual packages, or blacklist directories containing packages, as shown in /etc/slackpkg/blacklist.

rworkman · 12-16-2009, 08:15 AM

No, regex blacklisting isn't supported (yet?). It's something that I've been wanting (to do) for a while, and I think PiterPUNK wants (to do) it too, but time has been friendly to neither of us.

tuxdev · 12-16-2009, 10:38 AM

core-functions.sh:427

Code:

function checkblacklist {
   grep -Ev "[:space:]*#.*" "${CONF}/blacklist" |
   while read PATTERN ; do
      if test "$PATTERN" ; then
         local i
         local BLKNAME="${PKGDATA[1]}"
         for i in 2 3 4; do
            if echo "${BLKNAME}" | grep -Eq "${PATTERN}" ; then
               return 0
            fi
            BLKNAME="${BLKNAME}-${PKGDATA[$i]}"
         done
         if echo "${PKGDATA[6]/./}" | grep -Eq ${CONF}/blacklist ; then
            return 0
         fi
      fi
      false
   done
}

Seems to work for me, but rather slow, YMMV. May break things horribly since I just did it in 15-30 min without trying to understand the rest of slackpkg.

tuxdev · 12-17-2009, 08:43 PM

BTW, if this is actually supposed to be bash, not POSIX, then I'd use the =~ regex matching.

Old_Fogie · 12-18-2009, 12:49 AM

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:
1.kernel
2.packages
3.folders

So what if the blacklist file was changed to be four files:
1. blacklist.kernels
2. blacklist.packages
3. blacklist.folders
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.