ASDF configuration and cache

[Mark Evenson]

On 2015/4/29 07:13, Faré wrote:
> Dear Lispers,
> 
> The most significant bit for this email is:
> DO YOU HAVE A source-registry.conf ON WINDOWS?
> or do you know someone who has?
> If so, please contact me, either on this list or in private,
> because I'm considering a backward-incompatible change in its location.

[…]

For systems that build production code under Windows with ABCL running
asdf-3.1.4, we use the the user configuration directory
<file:~/.config/common-lisp/source-registry.conf.d/> (it always seemed
conceptually easier to have many small files that may be easily moved
than placing all the forms in a single
<file:~/.config/common-lisp/source-registry.conf>.)  At production
runtime, we explicitly "neuter" the ASDF configuration strategy via the
appropriate ASDF API, as we are running from within a Java web
application archive (to be described in a long overdue ABCL-DEV blog post).

As I understand your proposal, even though we don't use the
"source-registry.conf" file, we would still be effected by your proposed
change, as the value of XDG_CONFIG_HOME would be based on
%LOCALAPPDATA%, not %USERPROFILE% as is currently the case.

We would probably not use the XDG_CONFIG_HOME environment variable,
instead adapting to ASDF defaults, as it would be additional complexity
to describe to operations and one more thing that could go wrong.

As long as you make your proposed transition across a minor revision
(aka as ASDF 3.2.x), I do not have a problem with your proposal.  For
the record, although none of your listed benefits of this change would
give us any immediate advantage that I can determine, I support the
drive towards greater cross-platform uniformity.



-- 
"A screaming comes across the sky.  It has happened before, but there
is nothing to compare to it now."