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 28 April 2016.
01:48 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
MadcapJake ugexe: s/$.path/$.url/ ? 05:52
ugexe: wrt CURU, let's say that it can't find the Repository in the current repo-chain, should it die there? 05:55
or finish adding the repos and try again? (perhaps we would want to re-traverse the repo-chain every time a new repo has been resolved even?) 05:57
so many questions! :P 05:58
or maybe not the whole repo-chain but only the selection of newly added repos, to reduce unnecessary work 05:59
ugexe: thinking more on resolving all CURs, how would you say the first CUR would be handled? 06:15
07:32 domidumont joined 07:37 domidumont joined 07:53 lizmat joined
nine_ ugexe: it's a classic bootstrapping issue. You need a working repository chain to load the modules that implement repositories. 08:12
11:07 diakopter joined 13:50 sjn joined 14:10 sjn joined
MadcapJake I've done some refactoring and will work on the need-repo impls. tonight so hopefully I can submit a PR late this evening. 17:04
nine_ cool :) 19:06
[Coke] how do I delcare which version of the moar backend I want to use? 20:13
via rakudbrew (it has 2 moar backend options)
ugexe --configure-opts="--gen-moar=blah" or some such is a guess 20:46
[Coke] ugexe: no, I mean: there are two moar backends listed. 20:48
both called "moar"
ugexe oh, thats probably not right. i'd imagine each backend is meant to have a unique name (usually ending with -$commit or -$tag) 20:50
probably just need to open .rakudobrew/CURRENT and remove one of them 20:51
21:24 stmuk joined 22:05 sufrostico joined 22:59 sufrostico joined
[Coke] it's hardcoded in bin/rakudobrew 23:31