rpgoldman at sift.net
Sun Jul 12 17:24:40 UTC 2015
On 7/10/15 Jul 10 -3:24 AM, Mark Evenson wrote:
>> On Jul 10, 2015, at 05:05, Faré <fahree at gmail.com> wrote:
>> Nothing should have changed in the semantics of ASDF itself since the
>> last run of cl-test-grid, so I don't expect any discrepancy. We did
>> add better immutable-system support thanks to Dave Cooper, but that
>> isn't cover by cl-test-grid, only by our regression tests and his
> In a minor point on compatibility: I believe that [in the revision to the XDG
> machinery], under Windows the default location of the XDG config directory
> will change. Unfortunately, I have not had the time to verify that this is the
> case on my production ABCL instances under Windows.
> While I acknowledge that this change is a “bug fix” in ASDF’s interpretation of
> the XDG spec and the “correct” thing to do, it might help to be a little more
> verbose in the release notes on the ramification of a Windows-deployed end
> user’s upgrading from asdf-3.1.4 to asdf-3.1.5. Windows' lack of a symbolic
> links and NTFS semantics of not allowing a directory to be renamed when opened
> by a given process may make upgrading ASDF in-place for production instances a
> little tricky.
This sounds like a good point. Should we do this in the cover letter,
the changelog, manual, or some combination?
My guess is that relatively few people actually upgrade their ASDFs in
place -- most just get ASDF from their implementation. But that's not
an excuse for making them miserable.
Faré, do you have a sentence about the change in location that I could use?
> : https://gitlab.common-lisp.net/asdf/asdf/commit/7efd83582488c0cd4e3f0bb9aa1921d5fbfe9ec2
> Otherwise, onwards!
More information about the asdf-devel