(asdf:operate :build-op :system) creates image in ~/.cache/[...]

[Faré]

This was a bug in ASDF, that fails to call coerce-class on
component-build-operation
when comparing it to the current operation in bundle-output-files.

Fixed in 3.1.5.16.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Big Business has to *sell* the Vietnam War to you. Big Government can just
draft your ass and ship you overseas under threat of imprisonment and/or
death. Now, which one is better again? — rho at netdoor.com


On Sat, Sep 26, 2015 at 3:57 PM, Florian Margaine <florian at margaine.com> wrote:
> Hi list,
>
> I'm trying to use the relatively recent feature to dump an image using
> asdf's build-op feature, so that I only need this line in my terminal:
>
> sbcl --eval "(push \"$PWD/\" asdf:*central-registry*)" --eval
> '(asdf:operate :build-op :my-system)'
>
> Where my-system has the following .asd:
>
> (asdf:defsystem #:my-system
>   :description "foo"
>   :serial t
>   :depends-on (:sb-posix)
>   :components ((:file "package")
>                (:file "my-system"))
>   :build-operation "asdf:program-op"
>   :build-pathname "my-system"
>   :entry-point "my-system:main")
>
> The binary is built just fine. The issue is that it's created in
> ~/.cache/common-lisp/sbcl-1.2.15.debian-linux-x64/$PWD/, while I'd
> just like it to be created in $PWD/.
>
> Is this a configuration issue? Where is this setting configured?
>
> Regards,
>
> --
> Florian Margaine
>