Should I recompile sbopkg?

I like using sbopkg, although I sometimes run the build scripts from Slackbuilds from a command line. I've totally messed up my computer several times, upgrading to -current, and I did it again last night. Instead of repairing the install, I opted to reinstall with a Slackware -current oso from Alien Bob's repository. I have /home on a separate partition, anyway. So gcc is several renditions newer and I'm wondering if running sbopkg that was already compiled and packaged with the older version will play well with the newer compilers and the newer compiled software in Slackware -current.

Why not just update to latest version? I would use it until it seems to be a source of issues. But I'm lazy.

Updating is all good with developing packages sbopkg, afaict is pretty stable.

sbopkg is a script. no compiling needed.
You may want to redo packages created using it though, to "benefit" from gcc updates, if that was your question.

Originally Posted by timsoft sbopkg is a script. no compiling needed. You may want to redo packages created using it though, to "benefit" from gcc updates, if that was your question.

Yup, that's what I was thinking. I had saved a lot of the packages compiled under the older versions of gcc. So, when I got to looking at recompiling and repackaging some of them with sbopkg, I wondered if it might be better to recompile it as well. Surprisingly, Slackbuilds.org does not have a script for compiling and packaging sbopkg. Is that ironic?

Originally Posted by eyeinidas I wondered if it might be better to recompile it as well.

As others already said: there is nothing to REcompile in sbopkg, it contains only bash shell scripts and documentation

 $ file *
sbopkg: Bourne-Again shell script, ASCII text executable
sqg:    Bourne-Again shell script, ASCII text executable

BTW: this is true too for slackpkg, slackpkg+ and even the pkgtools "executables", they all
just are packages of pure scripts.

As for packages, compiled by sbopkg, just removepkg them and then reinstall and they will get compiled BY the newer gcc version.

Originally Posted by eyeinidas Surprisingly, Slackbuilds.org does not have a script for compiling and packaging sbopkg. Is that ironic?

I think it makes sense. slackbuilds.org is a third party repository of SlackBuild scripts which run fine from command line. Since it's third party, this is the reason why Slackware doesn't recommend it explicitly. Yet it has clean policies, sticks to the KISS principle and is seen as the de facto extension to vanilla Slackware (with the notable exception that is AlienBOB's personal repo). sbopkg is a third party tool for slackbuids.org scripts (but not the only tool), so probably this is the reason why it isn't mentioned on SBo explicitly as well.