Commit 12128dfc authored by Francois-Rene Rideau's avatar Francois-Rene Rideau

4.1.2: release!

parent ab81cc87
TODO for cl-launch as of 4.0.7.7
TODO for cl-launch as of 4.1.2
* When resuming from an image then dumping another, the INCLUDE_PATH
becomes a very bad variable to look for the image.
......@@ -38,13 +38,6 @@ TODO for cl-launch as of 4.0.7.7
unless explicitly requested a non-default implementation.
Maybe just add all the cl-launch features to buildapp.
* Support --dispatched-entry as from Xach's buildapp:
dispatched-entry would populate a data structure bound to
cl-launch::*dispatched-entry* and call a restart function
cl-launch::dispatched-restart that uses (argv0) on supported
platforms or via cl-launch launcher -- error out on unsupported platforms.
http://www.xach.com/lisp/buildapp/
* Support these other options from Xach's buildapp?
--load-path --asdf-path --asdf-tree --manifest-file --logfile
* asdf-path and asdf-tree would be accumulated into a source-registry
......@@ -77,3 +70,9 @@ TODO for cl-launch as of 4.0.7.7
The other half is scanning the source registry.
At least this scanning can be sped up, by patching ASDF
to support a source-registry cache or something.
* Improve release script to check and/or update that the date in
cl-launch.sh matches the date of the commit being released,
and generate cl-launch.1 from it using something.
pandoc? Ugly. ronn? Looks OK, if we replace its first lines
by our first line.
#!/bin/sh
#| cl-launch.sh -- shell wrapper for Common Lisp -*- Lisp -*-
CL_LAUNCH_VERSION='4.1.1.1'
CL_LAUNCH_VERSION='4.1.2'
license_information () {
AUTHOR_NOTE="\
# Please send your improvements to the author:
......@@ -88,7 +88,7 @@ PROGBASE="${0##*/}" # "$(basename "$0")"
CL_LAUNCH_URL="http://fare.tunes.org/files/cl-launch/cl-launch.sh"
HELP_HEADER="cl-launch.sh $CL_LAUNCH_VERSION \"(August 2014)\" \"Francois-Rene Rideau's\" \"shell wrapper for Common Lisp\""
HELP_HEADER="cl-launch.sh $CL_LAUNCH_VERSION \"(March 2015)\" \"Francois-Rene Rideau's\" \"shell wrapper for Common Lisp\""
print_help_header () {
ECHO "$HELP_HEADER"
ECHO "============"
......@@ -314,18 +314,18 @@ at which point it happens when you invoke the executable output file:
the primary return value of result is generalized boolean true, and
with status 1 if this value is \`NIL\`.
See documentation for \`UIOP:RESTORE-IMAGE\` for details.
* If option `-DE --dispatch-entry` is used, then the next argument must follow
the format `NAME/ENTRY`, where `NAME` is a name that the program may be
invoked as (the basename of the `uiop:argv0` argument), and `ENTRY` is
* If option \`-DE --dispatch-entry\` is used, then the next argument must follow
the format \`NAME/ENTRY\`, where \`NAME\` is a name that the program may be
invoked as (the basename of the \`uiop:argv0\` argument), and \`ENTRY\` is
a function to be invoked as if by --entry when that is the case.
Support for option `-DE --dispatch-entry` is delegated to a dispatch library,
distributed with `cl-launch` but not part of `cl-launch` itself, by
Support for option \`-DE --dispatch-entry\` is delegated to a dispatch library,
distributed with \`cl-launch\` but not part of \`cl-launch\` itself, by
(1) registering a dependency on the dispatch library as if
`--system cl-launch-dispatch` had been specified (if not already)
(2) if neither `--restart` nor `--entry` was specified yet, registering a
default entry function as if by `--entry cl-launch-dispatch:dispatch-entry'.
\`--system cl-launch-dispatch\` had been specified (if not already)
(2) if neither \`--restart\` nor \`--entry\` was specified yet, registering a
default entry function as if by \`--entry cl-launch-dispatch:dispatch-entry\`.
(3) registering an init-form that registers the dispatch entry as if
`(cl-launch-dispatch:register-name/entry "NAME/ENTRY" :PACKAGE)` had been
\`(cl-launch-dispatch:register-name/entry "NAME/ENTRY" :PACKAGE)\` had been
specified where PACKAGE is the current package.
See the documentation of said library for further details.
......
cl-launch (4.1.2-2) unstable; urgency=low
* Multiple entry binaries with --dispatched-entry,
mostly compatible with Xach's buildapp.
-- Francois-Rene Rideau <fare@tunes.org> Wed, 01 Apr 2015 01:09:11 -0400
cl-launch (4.1.1-1) unstable; urgency=low
* Portability: better fallbacks for implementations without a recent ASDF,
......
This diff is collapsed.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment