dawnrazor.net

Development has slowed on sbotools once again, which probably makes since given the size of the change-set for 1.5; this release is strictly a bug-fix release. Here are the highlights:

• A bug where sbotools unsafely assumed the existence of /tmp/SBo has been fixed (this looked like “readdir() attempted on invalid dirhandle $tsbo_dh” with some other details afterward).
• Support for $TMP being set in the environment has finally been implemented. SlackBuild files make use of this info, or fall back to /tmp/SBo; previously, we would not honour user changes to $TMP so all scripts used /tmp/SBo, which may not be what the user expects.
• A bug where trying to install something which doesn’t exist threw a meaningless error has been fixed (this looked like “Odd number of elements in hash assignment” with some other details afterward).
• A bug in the requirement checking code which could match something which was not a perl module against something installed via the cpan has been fixed.
• A bug which would, in certain conditions, cause the queue to be generated out-of-order, which could cause builds to fail to sboinstall trying to build something before its requirement has been built, has been fixed. Thanks to W. Li for reporting this.

An updated slackbuild has been submitted to slackbuilds.org; you can either wait for it to be accepted there then use sboupgrade to update to 1.6 (if you have 1.5 installed), or you can download the slackbuild from there and modify it for 1.6 and use it to update manually.

The local-modification changes are still planned, just with one thing and another, they have not yet been gotten to, but unless we find some more stupid bugs first, that will be the next thing worked on. In theory…

sbotools on dawnrazor.net
sbotools on SlackBuilds.org

sbotools 1.4 is now released, yes, less than a week after 1.3, but we have a lot of small fixes and enhancements in this release. Not all are user-visible, but here are the ones that are:

• When checking for installed requirements, sbotools is now aware of non-SBo packages. This means you can, for example, install jdk from /extra, and sbotools will see that as fulfilling an SBo’s requirement to have jdk already installed.
• When checking for installed requirements, sbotools is aware of CPAN-installed Perl modules. Note that not all CPAN-installed Perl modules register themselves in the system’s perllocal.pod, so sbotools won’t know about them, and in some cases SlackBuilds of Perl modules rename the module in bizarre ways, and sbotools won’t know about such renamings.
• A bug where attempting to build a compat32 package from something which had differing 32-bit and 64-bit download links would fail due to the slackbuild attempting to use the 64-bit source packages has been fixed.
• The requirement to have Text::Tabulate installed for sbotools is no more.
• sbocheck now writes a log, located at /var/log/sbocheck.log, of what updates it finds as available.
• A bug where sbotools was no longer aware of installed compat32 packages from SlackBuilds.org, due to a modification in how these packages get tagged, has been fixed.
• A bug where sbotools could not always “make clean” the source directories, or would do an incomplete job of it, has been fixed.
• sbotools will now attempt to download and md5sum verify all source files for all packages queued before attempting to build any of them.
• A bug where if a source fail already existed but failed md5sum verification sbotools would not remove it before wget’ing a new copy, resulting in the new copy having .1 appended and the md5sum verification still failing, has been fixed.

As I mentioned last release, we’re a lot more organized now, and it has helped a lot.

Moving forward, we’re looking at the different ways we can go about supporting local modifications to the tree, implementing a wiki, doing some refactoring/rewriting/cleanups, and (probably the very next thing we’ll do) implementing a new testing method which we figure ought to expose a number of interesting bugs that we don’t even know about yet.

Exciting!

Well, this is fairly overdue, considering that Pat bumped the slackware-version in -current to 14.0 a week and a half ago. Possibly the only noticeable difference in this release is that it now supports -current again, whereas 0.6 expects -current’s slackware-version to be 13.37.0.  In the meantime, there have many changes to the code itself. A lot of stuff has been cleaned up and refactored, a number of things have been made more robust, and some few hundred lines of code were removed. The code no longer handles temp files itself but uses File::Temp, which is better in virtually every way. A lot of little bugs were fixed along the way… but I didn’t keep track of which were pre-existing conditions and which were created along the way, so I can’t say those are bug fixes to the previous version as such.

And somewhere along the line I got into the idea of test-driven development, so that should, theoretically, mean the code is in better shape by definition… theoretically.

At any rate, click click.

sbotools 0.5 is now released. 0.5 brings the following changes:

• Requirement-parsing has been added to sboupgrade(1); when sboinstall(1) or sboupgrade(1)  are run WITHOUT the -r flag, the tool will look for a list of requirements in a given slackbuild’s README. For any found, it will check to see whether or not they are already installed, and if not, go through the list, asking whether or not the user wishes to install them. This is recursive, so that order is handled correctly. This is not foolproof, however, which is why requirement parsing does not happen when the README prompt is bypassed; you are expected to read and ensure the parsing functioned correctly. If you find a case where it did not, please let me know.
• A bug which caused temp files to not be deleted has been fixed.
• The bug from the previous post, where attempting to install a -compat32 package resulted in a 32-bit but not actually -compat32 package being installed (given -i was not specified), has been fixed.
• Comments have been added to the code for the sake of anyone wishing to assist or whatnot.

Given no serious bugs are found in this release, in the immediate future I will be focusing on some cleanup and refactoring that needs to happen, so the next release will likely take a little longer. This is necessary, however, to ensure the future of sbotools.

See the sbotools page for more information.

sbotools 0.4 is a maintenance release, bringing no new features. Here are a summary of the changes:

• The -j setting now gets validated, so that only a number can be fed to it.
• The .info files in some slackbuilds report an incorrect version, for example libreoffice.info says “3.5.3″, but the actual version is “3.5.3_en”; with the way I was previously determining the name of the package which was built, this would cause the package to not get installed at the end. That section has been rewritten so that incorrect versions in .info files do not present a problem.
• Several minor fixes, and more robustness.
• The code has been further cleaned up, re-organized, and refactored, though it still needs more.
• The man pages have been made more consistent overall.
• The sbotools.SlackBuild tag has been corrected, from “_SBo” to “_d4wnr4z0r”.

As always, please see the sbotools page for further information.