On Tuesday 25 February 2003 02:25 pm, Andreas Raab wrote:
> Debugging the problem I found the cause of this be
> ZipArchive>>extractMember:toFileNamed: which will _always_ extract
> to a relative path even if an absolute one is given. E.g.,
> evaluating something like:
>
>         aZipArchive extractMember: 'foo.bar' toFileNamed: 'D:\My
> Squeak\foo.bar'
>
> will actually result in putting the file foo.bar into '<image
> directory>\My Squeak\foo.bar'. This can't be right - if we give the
> archive an absolute path to extract something to, why would it
> forcefully interpret this as a relative one and even skip the
> drive?!
>
> This change must have happened recently as I have successfully
> installed this very package at various times in the past. I don't
> know if any other packages are affected by this but I think it's
> worthwhile to check.

I'll take a look at this.

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE