Re: RFC: writable private scratch XDG_CACHE_HOME in build enviroment?

[Mathieu Lirzin]

Hello Andy,

Andy Wingo <address@hidden> writes:

> Guile will try to automatically compile .scm files and cache them in
> XDG_CACHE_HOME.  When building Guile itself, Guile sets XDG_CACHE_HOME
> to ${top_builddir}/cache.  What if we would set this ourselves for all
> packages?  That way all packages could benefit from a scratch location
> when building that wouldn't propagate to the outputs.
>
> In Fibers I have some tests that I assume get compiled.  If they're not
> compiled, they go quite slow (260s vs 5s).  Alternately I could add a
> XDG_CACHE_HOME setting in Fibers.  Which should we do?

IIUC the problem you have is that in a Guix build environmnent, Guile
tries but *fails* to autocompile ".scm" files because it doesn't find
any directory that it can write on?

Even if I would not recommend relying on autocompilation in a build
process (or anywhere else) I agree that it would be reasonable to have a
way to autocompile ".scm" files in a Guix build environment.

Since /tmp is writeable in a Guix build environment and in most POSIX
systems (I guess), Would it make sense for Guile itself to fallback to
/tmp for its compilation cache?

Thanks.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37