I can understand doing this if the new package doesn't compile on the updated system, but if it does compile, I think it'd be much easier to just recompile the package (and dependencies, if needed) than trying to figure out what libs you're missing, finding those libs (hopefully they're official Slackware libs so they're easily grabbed out of packages), adding them to your system, creating any symlinks needed, and then updating ld.so.conf...

Maybe it's because I use some programs that rely on a lot of different libs, and it would take a while to find all the required libs and add them to the system. I'd much rather set up a queue, let sbopkg run through the night (I have an old computer) and then in the morning, it'll be as good as before.

Anyways, the idea is not to have to recompile 100 packages at once, but over the time as the new versions get released.

Those libs won't interfer with system libs. All newly compiled packages will use the new libs from the system lib directories.

Of course, it's important that you only copy the runtime libs and discard the other parts of the packages (no development headers, pkgconfig files, docs and other non-runtime stuff). What you need are versioned runtime libs and symlinks (libgif.so.2.0.0 and libgif.so.2 are ok, but libgif.so is not). Then everything works just fine.

One package is not the problem. 20 or 30 packages are. Not even counting the bulky dependencies like webkitgtk or wxPython.

It takes much less time to workout the dependencies for those than recompile everything. 15 minutes. Maybe more. Dependeing on the case. But not more than 30 mins.