[cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script

[Faré]

On 25/08/06, Luca Capello <luca at pca.it> wrote:
> Package: cl-launch
> Version: 1.85-1
> Severity: wishlist

I'm not sure we either need or want a /etc/cl-launchrc or a
~/.cl-launchrc. After all, the user (or root) may already export the
variable $LISP to override things at runtime (or at dump time),
whatever the --lisp or $LISPS variable be, unless explicitly prevented
with a --wrap argument (or a resetting of $LISP), and I think that's
all we need.

As for stumpwm, note that I prefer the more versatile --init argument:
   '(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))'
to a hardcoded :0.

If multiple dumped versions are wanted, they should each have a
different name, and the main script would select amongst them.

Finally, there are embarassing bugs in cl-launch 1.85, and I'd
appreciate it if one of my sponsors would have the time upload 1.86 to
unstable.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
You're currently going through a difficult transition period called "Life."