I think Xach and I are trying to cope with essentially the same problem:
lack of resources for a community project.
On the one hand, Xach wants to stick with and old ASDF because it's a
lot of trouble to maintain it, and he's afraid of breakage.
OTOH, we don't have the resources to maintain b
I just re-tested this on Mac, Linux and Windows, and everything I tried
passed. So I think we are good to release. I'll have another look at
updating the Changelog.
If anyone out there knows the right tooling for doing that, I'd
appreciate a pointer! I have been using the ChangeLog mode for
On Mon, Apr 9, 2018 at 12:22 PM, Robert Goldman wrote:
> On 9 Apr 2018, at 11:17, Attila Lendvai wrote:
>
>>> A cheesy fix would simply be to wrap it in IGNORE-ERRORS. But it might
>>> cause
>>> errors in its present form.
>>
>>
>>
>> i've learned, painfully, that indiscriminate ignore-errors will
On 9 Apr 2018, at 11:17, Attila Lendvai wrote:
A cheesy fix would simply be to wrap it in IGNORE-ERRORS. But it
might cause
errors in its present form.
i've learned, painfully, that indiscriminate ignore-errors will almost
always bite you back (in the form of wasted debugging time), no matte
> A cheesy fix would simply be to wrap it in IGNORE-ERRORS. But it might cause
> errors in its present form.
i've learned, painfully, that indiscriminate ignore-errors will almost
always bite you back (in the form of wasted debugging time), no matter
how innocent they look.
> This really is mor
On 7 Apr 2018, at 15:56, Robert Dodier wrote:
Thanks to everyone for their interest in this topic.
In reference to
https://github.com/quicklisp/quicklisp-client/pull/128/, it is only a
minimal stop-gap measure which I found could fix the immediate problem
which I encountered. I know very little