Adding local package results in malformed path (Windows)

On Windows, I think there is a bug with the location of say “Documents” on a different partition. I moved my Documents folder to a different partition. Steps to reproduce:

  1. Cd to E:\Documents
  2. Make a package foo (>]generate foo)
  3. Cd foo
  4. >]dev .

Gives an error

(@v1.5) pkg> dev .
[ Info: Resolving package identifier `.` as a directory at `E:\Documents\foo\`.
Path `.` exists and looks like the correct package. Using existing path.
  Resolving package versions...
ERROR: expected package `foo [ec961404]` to exist at path `C:\E:\Documents\foo`

In particular, it seems like it tries the C: drive whereas Documents is located on E:. Is this a bug or am I doing something wrong? Explicitly specifiying the full path does work.

I think it should be fixed on the upcoming 1.6. There was a problem with relative paths including the drive letter on Windows earlier.

Thanks, I’ll get back to you if the problem persists in 1.6