[Announce] sbotools 2.0
 

Hi all, I'm proud to announce the release of sbotools 2.0, which will work great with Slackware 14.2 (as well as 14.0 and 14.1).

It's been a long development cycle for Slackware and this means we've had time to implement some much needed new features in sbotools too! Compared to the 1.x series, the main new features are:

• Local overrides -- this allows you to maintain a local repository of slackbuilds that override what's on SlackBuilds.org.
• Custom repository support -- You can choose to use ponce's Slackware -current repositor for instance, or you can use the SlackBuilds.org git master repository rather than needing to wait for it to be published on the website.
• Sbosrcarch intergration -- If a download host is offline or giving you a corrupted file, sbotools will automatically try to fetch the source file from ftp://ftp.slackware.org.uk/sbosrcarch/ if it's available there.

We've also got tonnes of bugfixes, and some other minor new features in.

Without further ado, you can download the source tarball from here
and you can find a ready-made package which you can just installpkg right here

Unfortunately SlackBuilds.org haven't opened their submissions form yet, so we haven't been able to get it published there.



And if you're interested in understanding how to make use of the local overrides...



Some notes about local overrides
The overrides can be used both to make custom slackbuilds for your own use to override what's already on SlackBuilds.org, as well as letting you make a slackbuild for something that isn't even on there. For example, you could make a custom slackbuild of ffmpeg which instead of having a lot of optional dependencies, had as actual requirements all the dependencies you need. Or you could make a slackbuild for some software that for some reason or other doesn't belong on SlackBuilds.org.

To set up the local overrides
You'll first need to set up the path where your overrides will be and tell sbotools about it:
In that directory, every overridden slackbuild needs its own directory, so using the previous example of ffmpeg, you'd create the following directory structure:
and any other files the SlackBuild script needs to function.

After this, all the commands like sboinstall, sboupgrade, sbocheck, and sbofind will know to use the ffmpeg from your local overrides.


As always, please report any bugs or feature requests to https://github.com/pink-mist/sbotools/issues or the #sbotools irc channel on chat.freenode.net

Default value of `$repo_path` (which is `$config{SBO_HOME}/repo`) doesn't allow sbotools to use the same repo tree as sbopkg. 1.9 worked just great: I could use sbotools when there was a big dependency tree and sbopkg for more fine-tuned installation without having to maintain two SBo trees which were absolutely same. I had to edit `/usr/share/perl5/SBO/Lib.pm` to redefine `$repo_path` as just `$config{SBO_HOME}`.

Thanks for your awesome work suppy.

Great work, thank you!

Yes, I had to move the repository into a subdirectory in order to be able to support using custom repositories.

I thought sbopkg used /var/lib/sbopkg/ as their repository storage and that it had subdirectories for your slackware version in there, while sbotools uses /usr/sbo/repo ... however, what you could do, which I believe ought to work, is to make /usr/sbo/repo a symlink to /var/lib/sbopkg/SBo/14.2 ... if it doesn't though, I'm out of ideas..

Oh, I forgot to update this thread when sbotools 2.0 was made available on SlackBuilds.org, so a bit late, but:

sbotools 2.0 now available on SlackBuilds.org!

Thanks to the SBo team for providing such a valuable service!

Thanks for your great work suppy. Unfortunately I can't help, but I'm sure someday you will find a way to support download resume for those who don't have a speedy internet connection.

thanks for the great work, i have recently just found out sbotools :) but i'm loving it a lot so far. one question though, if i change a Slackbuild under /usr/sbo/repo/xxx does it take that in count when i compile? sbopkg let's me choose use the local or the default.

it will believe the file is the default one and simply run it as if it was; next time you update the repository though it's likely to get overwritten ... this is what the local overrides (mentioned in the first post) is for

Ok i see, i will use the local overrides instead to ger rid of the overwriting problem in the future :)

@suppy, Is it possible with sbotools to modify a .slackbuild and .info before processing, for example to get the latest version of a program like claws-mail or KeePass? I've already setup my PKG_DIR and REPO for ponce's -current by doing the following https://www.linuxquestions.org/quest...ig-4175589914/, but with sbopkg you can modify these two scripts before hitting the install process. Also NOTE that I am attempting to use on a multilib enabled system, is that a problem? I tried to build libgdiplus-4.2 and it failed today for a libgdiplus.la make ERROR 1 recipe error.
Otherwise I believe I'll have to manually do slackbuild.org process to build and then place the resulting package in local overrides, correct?
You thoughts are appreciated.

The sboinstall command just saved me major hassles when installing pandoc from SBo (along with all the Haskell deps). Thanks!

Found out the sboinstall has the -p option which is to install compat32, cool.
But not sure if there is a way to modify the slackbuild and info to change version for install?

just used it for the first time, could install something without even read the documentation, good tool(s)!

This tool really deserves to be better known. Thank you very much.