[Openmcl-devel] "dppccl --version" feature request

[Gary Byers]

On Wed, 21 Jan 2004, Rick Taube wrote:

> >
> > For your purposes, is "0.14" an adequate response to "--version" ?
>
> yes this would be fine! my script wants to install in a
> "<lisp>_<version>_<os-arch> dir that it creates if it has to. For
> example right now if it boots openmcl 0.41 on my osx machine the
> directory is
>
> pinhead:/Lisp/cm $ bin/cm.sh
> ; Loading
> "/Lisp/cm/bin/openmcl_0.14-031108_darwin-powerpc/clm-stubs.dfsl"
> ; Loading
> "/Lisp/cm/bin/openmcl_0.14-031108_darwin-powerpc/cmn-stubs.dfsl"
>
> the only way I could get that 'openmcl_0.14-031108' was by actually
> exec'ing openmcl (if it exists) and then parsing the
> (lisp-implementation-string) and then exiting. it would be sweet if I
> could just ask dppccl for a string that will be "unique" for fasls
> compiled by the same openmcl kernel.
>
>

So, what you'd like is for --version to return the same string that's
printed in the "Welcome" banner ?  E.g., if the next version calls
itself "0.14-040201", you'd like to see:

> openmcl --version
0.14-040201
>