I thought I asked this before, but I can't find the thread ... I'm using sbopkg to install SlackBuilds repo packages. `sbopkg -i` creates files in /tmp/SBo for each package. Do these directories need to be kept for any reason? Do future installs of the same package need the previous info in this directory?

You can delete it, but the next time you run a SlackBuild script from SBo, it will be created again. It's better to keep the directory and just clean out the contents if you don't need them anymore.

Well, I am referring to the contents of /tmp/SBo, not just that directory itself. So, it is OK to remove e.g. /tmp/SBo/openjdk and that will cause no issue with e.g. `sbopkg -c`, right?

Yes.

Personally, I usually just mount /tmp on tmpfs.

You can also change /etc/sbopkg/sbopkg.conf to automatically delete the extracted source and package creation directories after sbopkg finishes.

Change

to

3 members found this post helpful.

You're right. From your title, it sounded like you meant the /tmp/SBo directory itself, and I didn't read the actual post carefully enough. Yes, it's okay to delete the contents of /tmp/SBo, or, as bassmadrigal pointed out, you can have sbopkg do it automatically if you set CLEANUP=YES in sbopkg.conf.

Thanks, I'll certainly clean up what's out there. Thereafter, doing the CLEANUP=YES config settings seems like the way to go.

A semi-related question I hate to do a new post for ...

the sbopkg man page for option '-c' says , "Display a list of installed SBo packages and potential updates." However, I find that this option only displays potential updates. Packages I know I recently updated are not shown in this list. How do I show a list of all my installed packages?

yeah I've even did this
clean it out then reboot cuz somethings got a be in there during a session that I got rid of.
or

Well, I suppose that script will work if there is no official sbopkg option. Simpler then, is:

ls -ltr /var/log/packages | grep SBo

You can shorten it a bit and remove the grep by using wildcards.

Back again. What about /var/cache/sbopkg? Can that be cleaned out as well? It currently contains .zip, .gz, .bz2 and .xz files from old builds.

I did set CLEANUP=${CLEANUP:-YES} in /etc/sbopkg/sbopkg.conf and that does clean up the files in that folder.

That is where the source is downloaded to before it is extracted. Its contents can be removed, but there doesn't seem to be any option to automatically remove it after sbopkg finishes running.

1 members found this post helpful.

I hate to revive an old post, but I actually have a question about the removal of /tmp/SBo.

I've been using sbopkg with the -k option, which checks and skips installed packages. But when I removed /tmp/SBo, dependent packages that were already installed (in this case, numpy which is needed by Bottleneck) are apparently being reinstalled.

So it's not the case that files in /tmp/SBo are *never* needed again, but that they aren't needed at runtime. They might be used for building other packages, right?

These files should never be used again. The resulting packages are saved in just /tmp/, but, AFAIK, those shouldn't be used by sbopkg again either.

AFAIK, sbopkg does not reinstall packages that were previously built. If ran with the -k option, sbopkg will skip anything that's currently installed, but if it isn't installed, I don't think it'll check for a built package in /tmp/ and I know it doesn't check for anything in /tmp/SBo, because I have it happen frequently when I'm rebuilding things and it will just proceed like normal and delete the source and packaging directories if they exist.

I've not dug into sbopkg enough to know for sure, but I believe I am accurate.

That being said, sbopkg won't check for any packages that don't have the SBo tag in the package name. So if you happened to install a numpy from a different repo, sbopkg would try and build it again if it was in the queue.

1 members found this post helpful.