|
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 3 August 2017. |
|||
|
01:53
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 | ||
|
03:16
http_GK1wmSU joined
03:17
http_GK1wmSU left
04:56
lizmat joined
08:57
edehont joined
16:01
sivoais joined
16:41
edehont joined
|
|||
| ugexe | nine: I'm wondering if multiple perl6 installs can't work (currently) with ~/.perl6 and automatic repo format upgrading | 17:40 | |
| the repo is effectively broken for an older install once it has been upgraded | 17:41 | ||
|
17:42
hoelzro joined
|
|||
| ugexe | gist.github.com/ugexe/dc3963f4ed7a...ri-pm6-L18 | 17:50 | |
| 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:52 | ||
| of course having 2 different repo versions mixed will just be a different shit show | 17:53 | ||
| 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) | 17:56 | ||