On 5/1/10 9:26 PM, Faré wrote:
> Dear Mark,
>
> thanks a lot for your patch. Your efforts are appreciated.
>
Not as much as I appreciate your unflagging energy (and time) towards
shipping ASDF2. You will be missed after you ship this puppy!
> On 1 May 2010 14:04, Mark Evenson wrote:
>> Attache
I realize that the following patch in needed in 1.713. Mark, can you
comment on whether it's always safe to use /___jar__root__file___/
without risk that a host/device will be imported from
default-pathname-defaults when I truenamize it?
- (relativize-pathname-directory p)
+ (relativize
I merged something as 1.712. Please test with ABCL.
Unlike the version that you had going through namestrings of
make-pathnames, it shouldn't have the pitfall of horrors when the
*default-pathname-defaults* supplies an interesting device. Just like
your version, though, it probably supposes that /f
Dear Mark,
thanks a lot for your patch. Your efforts are appreciated.
On 1 May 2010 14:04, Mark Evenson wrote:
> Attached please find a patch which fixes problems pointed out by Carlos
> Ungil when ABCL would catastrophically fail to translate the output location
> for ASDF systems located withi
Attached please find a patch which fixes problems pointed out by Carlos
Ungil when ABCL would catastrophically fail to translate the output
location for ASDF systems located within jar files under Windows.
We've fixed this in the version of ASDF 1.679 which we are planning to
ship as part of a
