3.2

This latest version of sbotools contains one new feature:

• Optionally verify git commits and rsync pulls; set GPG_VERIFY to TRUE

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 than sboconfig (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 between LOCAL_OVERRIDES and the SBo repository

Other changes include:

• sbocheck: Do not use compact formatting when CLASSIC mode is on
• Utill.pm: Read sbotools.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.