On 12 Oct 2017, at 12:09, 73budden . wrote:
This tracing tool should help a lot.
I believe this tool should be supplied by asdf team. Even I begin to
be more positive towards efforts of ASDF team to clean up all the mess
that was in ASDF initially, but obviously society is not quite happy
with
On Thu, Oct 12, 2017 at 6:53 PM, Stelian Ionescu wrote:
> On Thu, 2017-10-12 at 13:03 -0500, Robert Goldman wrote:
>> That may be, but it was unfair to get angry at the ASDF maintainers
>> about this. This is just a pre-existing error that was *manifested*
>> because of a
On Thu, 2017-10-12 at 13:03 -0500, Robert Goldman wrote:
> That may be, but it was unfair to get angry at the ASDF maintainers
> about this. This is just a pre-existing error that was *manifested*
> because of a change in ASDF. It's not our fault that this error
> appeared, it's not our fault
On Thu, Oct 12, 2017 at 6:11 PM, Robert Goldman wrote:
>> I will merge this into master, but do not have time to make a new release,
>> or even test much this week or next.
>>
>> So this will simply remain in master for now.
>
> This patch is now available in ASDF 3.3.0.1
>
I
On 12 Oct 2017, at 13:08, Robert Goldman wrote:
On 12 Oct 2017, at 13:04, Faré wrote:
For those in a hurry for a fix, here is the merge request:
https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85
I will merge this into master, but do not have time to make a new
release, or even
Wow! Good news.
2017-10-12 21:08 GMT+03:00, Robert Goldman :
> On 12 Oct 2017, at 13:04, Faré wrote:
>
>> For those in a hurry for a fix, here is the merge request:
>> https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85
>
> I will merge this into master, but do not
On 12 Oct 2017, at 13:04, Faré wrote:
For those in a hurry for a fix, here is the merge request:
https://gitlab.common-lisp.net/asdf/asdf/merge_requests/85
I will merge this into master, but do not have time to make a new
release, or even test much this week or next.
So this will simply
On Thu, Oct 12, 2017 at 5:09 PM, 73budden . wrote:
> Warning about modifying standard readtable is issued by SBCL (at least
> in my SBCL 1.3.18), please grep for the message in SBCL sources, and
> it seem to be introduced in 1.0.24. I took a look at puri's definition
> (maybe
off to?
2017-10-12 11:45 GMT-06:00 Robert Goldman <rpgold...@sift.info>:
Forwarded message:
From: 73budden . <budde...@gmail.com>
To: Robert Goldman <rpgold...@sift.info>
Cc: Faré <fah...@gmail.com>, ASDF-devel
<asdf-devel@common-lisp.net>
Subject: Re: [E] new c
Warning about modifying standard readtable is issued by SBCL (at least
in my SBCL 1.3.18), please grep for the message in SBCL sources, and
it seem to be introduced in 1.0.24. I took a look at puri's definition
(maybe old, in my local copy of quicklisp) and it looks like it
actually tries to
Warning about modifying standard readtable is issued by SBCL (at least
in my SBCL 1.3.18), please grep for the message in SBCL sources, and
it seem to be introduced in 1.0.24. I took a look at puri's definition
(maybe old, in my local copy of quicklisp) and it looks like it
actually tries to
I'm with Faré on this one. I don't see evidence that this change is
because ASDF is doing something bad. I believe it's consistent with the
hypothesis that there was some imperfectly-controlled aspect of building
that is done differently now (e.g., files loaded in a different order
where
12 matches
Mail list logo