spftools is a set of utilities for maintaining foreign packages under
slashpackage
.
These tools let you install foreign packages—those that are not
designed for installation under /package
—in
/package
, much as you would do with rpm
,
apt
, etc., for their respective package formats.
This package is discussed on the spf list. New releases are announced on the prjware-announce list.
spftools 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 2010.01.03).
Older versions are published for historical interest.
You can get the latest development sources with:
$ git clone git://git.dogmap.org/spftools.git
To run spftools, you need my sptools package.
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 run sp-install
:
# sp-install spftools-VERSION.tar.bz2
Or, if you like to do things manually, unpack the tarball and run
package/install
:
# cd /package # bunzip2 < /path/to/spftools-VERSION.tar.bz2 | > tar -xpf - # cd admin/spftools-VERSION # package/install
Read package/README
and package/INSTALL
for more
detailed instructions.
spf-download
program
downloads package tarballs.
spf-install
program
installs packages.
spf-path
program
spf-unpack
program unpacks
package tarballs.
$SP_UPGRADE_DEPS=n
, spf-install does not verify that
dependencies satisfy the version requirements of the package given on the
command line, or that they are even installed.*-config
programs to report the
dependent's .../conf/*
path instead of the library's own
prefix.