Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-03-06

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:48 ilbot3 joined #perl6-toolchain
02:48 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
06:55 domidumont joined #perl6-toolchain
08:03 llfourn joined #perl6-toolchain
08:24 llfourn joined #perl6-toolchain
09:07 domidumont joined #perl6-toolchain
09:14 sivoais joined #perl6-toolchain
09:14 domidumont joined #perl6-toolchain
09:35 llfourn joined #perl6-toolchain
12:29 domidumont joined #perl6-toolchain
13:15 domidumont joined #perl6-toolchain
14:29 GK___1wm_SU joined #perl6-toolchain
15:23 ugexe Probably doesn't matter, but I just had a thought: if you have two versions of rakudo that use different repo-versions but share a CURI location then things are probably going to blow up
15:24 ugexe Maybe we need a Distribution::Installable[$repo-ver = 2] type deal to handle repo versions instead of transforming the repo itself?
15:29 ugexe instead of transforming the files directly it would need to reinstall each Distribution when rakudo upgrades though
15:34 ugexe meh that leaves old rakudo without the Distribution to understand those
16:53 domidumont joined #perl6-toolchain
17:04 nine Maybe we'll just run out of reasons for upgrading the repo in the first place :)
17:38 domidumont joined #perl6-toolchain
18:18 FROGGS joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary