Comment 4 for bug 604728

The use case is as above: I've built a core and the fasls are now irrelevant-- the system shouldn't depend upon intermediate objects being in place.

The fasls aren't where lisp expects them because I build the cores and the rest of my development team uses them. The new output-translations layer places the fasls from my compilation in a private cache not visible to the other developers.

As a workaround I've configured output translations to have a shared cache (see the documentation error in https://bugs.launchpad.net/bugs/485918) so that the fasls are in the same place for all of us. Even with this it is finicky to the point I'm thinking of just dropping the core building as less reliable than the gain.

I did dig through the code enough to see that about the only logic for load-op was to depend upon compile-op so that it isn't going to be a trivial patch. Wishlist is fine, I just wanted it documented as it is a very non-intuitive behavior of the system.