Re: Compiling Lisp

Javier <javuchi@xxxxxxxxx> wrote:
If you distribute your application for Linux, it is better to
include a fasl file with a little script starting SBCL, inside a RPM or
DEB package, and a dependency to the SBCL package itself.

That doesn't sound like a very good idea.

SBCL fasls are version-specific, so the user would need to get an RPM
for exactly the right version of SBCL. A careless "yum update", and,
oops, the application no longer works. Or if somebody needs to install
two applications distributed as fasl files, which were built using
different SBCL versions, he'd also have to install those two SBCL
versions installed on the same machine.

--
Juho Snellman
.

Relevant Pages

  • Re: Compiling Lisp
    ... include a fasl file with a little script starting SBCL, ... DEB package, and a dependency to the SBCL package itself. ... so the user would need to get an RPM ...
    (comp.lang.lisp)
  • Re: Compiling Lisp
    ... include a fasl file with a little script starting SBCL, ... DEB package, and a dependency to the SBCL package itself. ... so the user would need to get an RPM ...
    (comp.lang.lisp)
  • Re: Compiling Lisp
    ... include a fasl file with a little script starting SBCL, ... DEB package, and a dependency to the SBCL package itself. ... so the user would need to get an RPM ...
    (comp.lang.lisp)
  • Re: Compiling Lisp
    ... include a fasl file with a little script starting SBCL, ... DEB package, and a dependency to the SBCL package itself. ... so the user would need to get an RPM ...
    (comp.lang.lisp)
  • Re: Lets talk about GUI and sound libraries
    ... is in native code fasl file format version 64, but this version of SBCL ...
    (comp.lang.lisp)