...that is, also include the file prefix.def, which specifies where
the system is configured to install. Now that I think of it, it might
be more elegant to be able to query the runtime about its default
SBCL_HOME, actually...
Thanks to Bruce O'Neel.
b=${1:?"missing base directory name argument"}
tar -cf $b-binary.tar \
- $b/output/sbcl.core $b/src/runtime/sbcl \
+ $b/output/sbcl.core $b/src/runtime/sbcl $b/output/prefix.def \
$b/BUGS $b/COPYING $b/CREDITS $b/INSTALL $b/NEWS $b/README \
$b/install.sh $b/find-gnumake.sh $b/sbcl-pwd.sh $b/run-sbcl.sh \
$b/doc/sbcl.1 \
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.41.53"
+"1.0.41.54"