Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-08-04

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

All times shown according to UTC.

Time Nick Message
01:53 ilbot3 joined #perl6-toolchain
01:53 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
03:16 http_GK1wmSU joined #perl6-toolchain
03:17 http_GK1wmSU left #perl6-toolchain
04:56 lizmat joined #perl6-toolchain
08:57 edehont joined #perl6-toolchain
16:01 sivoais joined #perl6-toolchain
16:41 edehont joined #perl6-toolchain
17:40 ugexe nine: I'm wondering if multiple perl6 installs can't work (currently) with ~/.perl6 and automatic repo format upgrading
17:41 ugexe the repo is effectively broken for an older install once it has been upgraded
17:42 hoelzro joined #perl6-toolchain
17:50 ugexe https://gist.github.com/ugexe/dc3963f4ed7ac8e0c0782fd2af9a2067#file-curi-pm6-L18
17:52 ugexe this is one way to solve it - by not upgrading the repos, letting some Distribution that knows how to parse some version handle all that, and CU just needs to figure out the repo version and which Distribution to use
17:53 ugexe of course having 2 different repo versions mixed will just be a different shit show
17:56 ugexe so for that idea to work it'd have to keep those Distribution implementations in lib/, so that they get installed to ~/.perl6 (with the idea the older rakudos could then understand the newer repo version)

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