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:
Code:
sboconfig -o /path/to/overrides
In that directory, every overridden slackbuild needs its own directory, so using the previous example of
ffmpeg, you'd create the following directory structure:
Code:
/path/to/overrides/ffmpeg/ffmpeg.info
/path/to/overrides/ffmpeg/ffmpeg.SlackBuild
/path/to/overrides/ffmpeg/README
/path/to/overrides/ffmpeg/slack-desc
...
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
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.
