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 5 August 2017.
01:52 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: yes, this finally nailed it :) 08:17
13:09 http_GK1wmSU joined 13:10 lizmat joined 13:11 http_GK1wmSU left 18:08 lizmat joined
japhb Does the mi6 developer hang around here? 18:24
lizmat don't think so, but I'm told he hangs around on #perl6 and/or #perl6-dev, although his nick escapes me atm 18:26
japhb Dang 18:27
OK
19:18 tbrowder joined 20:47 tadzik joined
ugexe nine: 6th time is always the charm 21:14
now im working on CURFS, but the question of what to do when $!prefix does not contain a meta puzzles me. From a purity standpoint things like %?RESOURCES should simply not work - if you want to use such things then you must include the meta data. Otherwise -Ilib really means "check the parent directory for a META6.json first" which might not be the right thing to do 21:17
i would say that -I. would handle all of that (where CWD contains a meta6.json) and -Ilib would only work for the most basic things 21:19
the presence of a META6 should allow it to be treated as a Distribution, the lack of one should allow it to only be treated as a single CompUnit 21:21
this could only be changed in 6.d though 21:22
I have hooked up a .candidates to CURFS though, which also means it can consider module versions/api/auth *if* they include meta data gist.github.com/ugexe/c5d864f287b4...58657c655d 21:26
it might seem strange to have such a method on a repo that technically is representing only one distribution, but this logic needs to happen anyway to resolve so may as well expose it like with CURI 21:27