Releases: pghvlaans/sbotools
3.3
This release does not have much in the way of feature addition, instead focusing on under-the-hood reliability improvements:
- In line with the
SBO_HOME
changes in version 3.2, all scripts except forsboconfig
will exit if incorrect configuration options are detected Build.pm
: Remove the temporary directory fortee
in case of signalRepo.pm
: Check for local repo similarity to SBo rather than solely relying on SLACKBUILDS.TXT- Wrap most variable-length onscreen messages, prompts and error reports from
sbotools
at 72 characters
If you are experiencing "cannot be parsed" errors with an upstream SBo repository, this should now be fixed:
- Bugfix: When parsing info files, sanitize them for whitespace, unwanted lines, quotes and backslashes
With the changes to local repo detection rendering it redundant, sbosnap
was replaced with a compatibility symlink to sbocheck
. sboconfig
and sbocheck
saw a few changes:
sboconfig
: Permit versions "X.Y+" and "current" forSLACKWARE_VERSION
; leave more informative error messagessboconfig
: Use--reset
to restore all default settingssbocheck
: Before fetching the repo, prompt the user if the desired branch does not exist
Finally, build number detection has been improved, resulting in performance gains for sbocheck
.
Thank you to @Geremia and @pandom79 for reports #18 and #19!
3.2.1
3.2
This latest version of sbotools
contains one new feature:
- Optionally verify git commits and rsync pulls; set
GPG_VERIFY
toTRUE
Like slackpkg
, sbotools-3.2
can add public keys to the root keyring. Missing keys have their information displayed and are added only upon user prompt.
Another area of focus was improving usability when SLACKBUILDS.TXT
goes missing or git fetches go wrong. Relying less on SLACKBUILDS.TXT
is a goal for the next version, but the following changes to Repo.pm
have gone in:
- Prompt for file regeneration if
SLACKBUILDS.TXT
does not exist instead of displaying the cryptic/usr/sbo/repo exists and is non-empty
error - Remove the antiquated
migrate_repo()
subroutine, which could potentially eat the GPG log - Offer to retry failed git fetch
A few bugfixes are in as well, the older and more important of which relate to bad sbotools.conf
settings. Although sboconfig
does its own linting, editing the file directly is probably a more intuitive means of changing settings for most. Linting capabilities may be expanded further in the future.
- Lint the value of
SBO_HOME
before running anything other thansboconfig
(particularly, using a relative path could leave stray copies of the repository all over the file system) - Do not crash for improper values of
SLACKWARE_VERSION
sbocheck
properly reports version differences betweenLOCAL_OVERRIDES
and the SBo repository
Other changes include:
sbocheck
: Do not use compact formatting whenCLASSIC
mode is onUtill.pm
: Readsbotools.hints
only once, and allow multiple optional dependency specifications for the same script
Last but not least, a goal of this fork has been to improve the documentation. The pod
material for the SBO::Lib::*
modules has been edited for style and accuracy, and development-oriented man pages are now installed to section 3.
Thanks are due to @dchmelik for reporting the SLACKWARE_VERSION
error, to @Charadon for requesting development documentation and to Slack Coder for proposing GPG verification.
3.1
It's a little late for everyone's python-3.12
rebuild on -current and a little early for the Slackware 15.1 release, but sbotools-3.1
is here all the same.
The standout new feature this time around is the addition of a configuration file in /et/sbotools/sbotools.hints
, which can blacklist scripts and notify sbotools
of any desired optional dependencies on a per-script basis (before or after building). Not sure if, say, libiscsi
can actually be removed from the system? Wonder no more. sboremove
and sbofind -R
honor sbotools.hints
.
Aside from that, sbofind
now takes more than one search term, sboinstall --mass-rebuild
will rebuild all in-tree _SBO
packages on the system (resumable in case of failure or stoppage) and the handling of the next Slackware version has been shored up for when the time comes. sbocheck
has more compact output, the documentation now includes a summary sbotools.1
page and there are also a handful of bugfixes.
- sbofind: Allow multiple search terms
- Add a summary sbotools(1) man page with executive summaries and a startup guide
- sboinstall: Use --mass-rebuild to rebuild all non-compat32 SlackBuilds
- sboconfig: Fix incorrect misconfiguration warnings
- sbocheck: More compact output.
- sbotools.hints: User-specified blacklist and optional dependency requests
- Bugfix: Prevent undefined build number checks with a local override directory
- Bugfix: Add a missing
git pull
for custom git branches - sboinstall: Use a resume file for --mass-rebuild
- Clarify LOCAL_OVERRIDES documentation
- Detect and handle next version (currently 15.1) more effectively
- Adopt the MIT License
3.0
This is the third release for the pghvlaans fork, and the first under the name sbotools
. It includes a handful of new features, most notably including a "Classic Mode" for users who are interested in a look-and-feel more similar to sbotools-2.7
.
sbocheck
: Use --nopull to check for updated SlackBuilds without updating the treesboremove
: Remove undocumented nointeractive optionsbofind
: Use --reverse to check for installed reverse dependencies- Add setting CLASSIC; turn on BUILD_IGNORE and RSYNC_DEFAULT, and disable output added after
sbotools-2.7
- Fix some --help verbiage
1.1
1.0
This is the initial release of sbotools3
, the continuation of sbotools
.
A debt of gratitude is owed to the original author, Jacob Pipkin, longtime maintainer Andreas Guldstrand and major contributor Luke Williams. This software would not exist without their efforts.
sbotools
has gone without commits for a number of years. During this time, the default URL for release Slackware beyond 14.2 became unusable, and building compat32 and 32-bit packages on multilib systems stopped working for nearly all SBo SlackBuilds. Both of these issues have been fixed in sbotools3
.
- Bugfix: 15.0-compatible collection of default URLs
- Bugfix: Build non-i486 compat32 packages
- Bugfix: Build compat32 packages from template
Nonetheless, this repository was originally a simple fork adding a feature: Saving previously-used build options to be shown to the user when installing a SlackBuild again. In that spirit, the main focus of sbotools3
has been to implement new functionality, some of which was originally planned by @pink-mist.
- Use a customizable git branch to clone the local repository
- New git-based default URLs, with the option to use default rsync URLs instead
- Optionally upgrade on build increments and report out-of-tree SlackBuilds
- Save build options and offer to re-use them
- Install bash completions to go with the existing zsh completions