sbcl
(load "~/quicklisp/setup.lisp")
(asdf:INITIALIZE-OUTPUT-TRANSLATIONS)
;; So far, so good:
((#P"/home/tunes/local/stow/sbcl/lib/sbcl/**/*.*" T)
(#P"/home/tunes/local/stow/sbcl/lib/sbcl/**/*.*"
#P"/home/tunes/local/stow/sbcl/lib/sbcl/**/*.*")
(T T)
(#P"/home/tunes/.cache/common-lisp/sbcl-
Faré writes:
>>> PS: is it only me, or is quicklisp disabling output translations for its
>> Its what? Postscripts?
> fasls.
>
> The fasl paths are not translated (at least not for me), and e.g.
> allegro and sbcl will clash, since they both name their fasls .fasl.
I don't think Quicklisp disabl
>> PS: is it only me, or is quicklisp disabling output translations for its
> Its what? Postscripts?
fasls.
The fasl paths are not translated (at least not for me), and e.g.
allegro and sbcl will clash, since they both name their fasls .fasl.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethic
Faré writes:
> PS: is it only me, or is quicklisp disabling output translations for its
Its what? Postscripts?
Zach
>> I'm actually not sure what the assumptions are for QL. Does it assume
>> that all libraries should be portable? Can contributors proclaim their
>> systems to be non-portable, and does that affect QL function (and if so,
>> how)?
>
> The current situation is that the project must build on SBCL,
