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

[Faré]

I put on my site a cl-launch 1.87 deb that I believe fixes 384697.
Testers: Please test.
Uploaders: please upload.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
If Java had true garbage collection, most programs would delete themselves
upon execution. -- Robert Sewell


On 29/08/06, Faré <fahree at gmail.com> wrote:
> Due to popular request, I am working on an optional /etc/cl-launchrc
> feature for cl-launch.
> Because I allow a --no-rc option (that is enabled by default for me,
> you can use --rc by default), the contents of these file will be read
> *after* the option processing.
>
> A cl-launchrc file may contain statements such as:
> system_preferred_lisps stumpwm cmucl sbcl clisp
> system_preferred_lisps exscribe clisp cmucl
>
> Then remains the question of whether or not the statements should
> override a user-specified --lisps option. My current feeling is "yes,
> but issue a warning on stderr".
>
> Also, the preferrence happens at script-creation time. At runtime, the
> variable $LISP is still all that matters -- should it not?
>
> [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
> Clairvoyant, n.:
>         A person, commonly a woman, who has the power of seeing that
> which is invisible to her patron -- namely, that he is a blockhead.
>                 -- Ambrose Bierce