Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
Set by moderator on 10 June 2016.
01:10 TimToady joined 01:49 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
nine ugexe: oh, that's indeed a clear oversight! 07:56
ugexe: CUR::AbsolutePath is really just for require "/foo/bar.pm"; This used to be handled by CUR::FileSystem but that required at least one of those in the repo chain and it muddled responsibilities. 07:58
08:10 domidumont joined 08:15 domidumont joined 09:21 camelia joined 10:01 FROGGS joined 13:50 b2gills joined 16:58 domidumont joined
ugexe Is there any way to add debug output to CU::PS::File? If I add `note`s the output works during `make install` but gets stuck here (github.com/rakudo/rakudo/blob/7a98...y.pm#L219) when running zef (while precompiling the first module) 17:08
if i remove :err from the call to `run` and comment out the 2 instances of $proc.err in CU::PR then it does not get stuck 17:38
17:45 stevieb joined 17:52 stevieb joined
ugexe that last one is a bug with run 18:00
Here are the changes i've come up with so far: github.com/rakudo/rakudo/compare/n...s?expand=1 18:13
$proc.err cant be `slurp-rest`ed (forking error), hence the $proc.err.lines.join("\\n") 18:15
but $proc.err has to have it contents read to avoid getting stuck at where i mentioned earlier 18:16
that changes the `require <Build.pm>` error message from "Failed" to the better "No such symbol 'Build'" 18:26
19:06 edehont joined