sptools

Releases

sptools is devoid of warranty and is distributed under the GNU General Public License, version 2. But that doesn't mean it's necessarily a good idea for you to distribute modified versions. I'd like to know if you plan to do that.

This link always points to the latest version (currently 2020.05.03).

Older versions are published for historical interest.

You can get the latest development sources with:

$ git clone git://git.dogmap.org/sptools.git

Dependencies

None.

Installation

slashpackage is a good thing. You can read more about it here. If you don't already have /package, create it (on any filesystem you like, as long as it's accessible by the name “/package”):

# mkdir -p /usr/local/package
# ln -s /usr/local/package /
# chmod +t /package/.

Then, if you already have sp-install, you can use it:

# sp-install sptools-VERSION.tar.bz2

Otherwise (or if you like to do things manually), unpack the tarball and run package/install:

# cd /package
# bunzip2 < /path/to/sptools-VERSION.tar.bz2 |
> tar -xpf -
# cd admin/sptools-VERSION
# package/install

Read package/README and package/INSTALL for more detailed instructions.

Documentation

• The sp-check program looks for unusual files under /package.
• The sp-download program downloads a package tarball.
• The sp-freeze program locks dependency symlinks to point to specific versions.
• The sp-globals program compares the contents of /command to the per-package command directories.
• The sp-install program installs a package.
• The sp-links program creates symlinks in /command pointing to files in per-package command/ directories.
• The sp-unpack program unpacks a package tarball.
• The sp-version program sets the current-version symlink for a package.

Current known bugs

None.

To do

• Make sp-globals list extraneous symlinks in the global directory. But sh can't do this fast enough. C? Scheme?
• Make a tool to list symlinks that would break if a given package were removed.