Nick Logan
Nick Logan
I just remembered I've already done a lot of work in this area as well. Probably some stuff here worth considering: https://github.com/perl6/roast/compare/cur-candidates
1) Not sure. Could possibly just mark the tests that don't yet work as `todo` instead of the entire file. 2) 3) `rm_rf` would probably be a handy `Test::Util` tool....
As you mentioned this is outside the scope of zef, although ultimately yes it should become globally solved via some build module which zef can use. The Perl6 world currently...
Here is a proposed solution to this issue: https://github.com/perl6/toolchain-bikeshed/blob/master/build.md
`:` isn't safe to use on e.g. Windows filesystems, but archive names should be as platform independent as possible. Actually I guess `%` isn't either (which I thought was ok)...
That being said: I think that zef tar plugin should avoid the remote feature one way or another.
S22 suggested naming like `JSON-Fast-v1.tar.gz` -- of course using a `-` as a separator doesn't work for a number of other reasons but does suggest the naming was somewhat considered...
It looks like both bsdtar and gnutar support `--force-local`, but I don't see it for busybox tar. On Windows `C:Projects\` is relative path which is the only reason I'm wary...
Unfortunately Windows doesn't allow `%` in file names so percent encoding probably isn't going to help afterall.
fwiw I have a fix, but appveyor continues to fail in the exact same spot when testing `PathTools` and I don't know why. It was pointed out the length of...