OK, I'm setting the day and time for the next ASDF debugging session
to Tuesday January 2nd 2018 at 14:00 EST (19:00 UTC). Please send me a
private email if you can make it, I'll add you to a Google Calendar
event with a Hangout invitation.
—♯ƒ • François-René ÐVB Rideau •Reflection•
On Wed, Dec 27, 2017 at 10:33 AM, Robert Goldman wrote:
> On 4 Dec 2017, at 21:56, Faré wrote:
>
>> Fixing the same potential issue with the (more stable but still
>> evolvable) code in the core of ASDF will require applying the same
>> solution to action.lisp all files that
In the future, when debugging something like this, where the environment
into which you are loading code is of critical importance, and an ASDF
issue is suspected, I suggest the following:
On the various implementations, do whatever you need to do to prepare to
load the system that exhibits
On 20 Dec 2017, at 19:48, Faré wrote:
It looks like there is a bug in ASDF 3.3 worth definitely worth fixing
before I leave:
https://bugs.launchpad.net/asdf/+bug/1739514
Basically, ASDF fails spuriously rebuilds misnamed secondary systems
and/or things that depend on them, instead of just
On 4 Dec 2017, at 21:56, Faré wrote:
Fixing the same potential issue with the (more stable but still
evolvable) code in the core of ASDF will require applying the same
solution to action.lisp all files that define new operations.
Will you please clarify this sentence? It looks like some
On Tue, Dec 26, 2017 at 7:43 PM, Ken Tilton wrote:
> But I am curious, I will first try to see why uninstall did not work.
When you first install Quicklisp, it will download the latest dist. A
dist is, among other things, a list of URLs pointing to project
snapshots that are