Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-02-27

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

All times shown according to UTC.

Time Nick Message
00:14 llfourn joined #perl6-toolchain
02:38 llfourn joined #perl6-toolchain
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:34 llfourn joined #perl6-toolchain
07:33 llfourn joined #perl6-toolchain
09:08 domidumont joined #perl6-toolchain
11:55 domidumont joined #perl6-toolchain
12:53 domidumont joined #perl6-toolchain
13:55 SmokeMachine joined #perl6-toolchain
15:02 lizmat joined #perl6-toolchain
15:24 nine ugexe: resolve-unknown-repos does not work yet as smoothly as it should. I hit issues in that area when trying to create rpm packages for Inline::Perl5. It's important that no none of the precompiled code and objects refer to the custom repo in any way.
16:27 lizmat_ joined #perl6-toolchain
16:33 lizmat joined #perl6-toolchain
16:45 ugexe nine: so if I have custlib#/foo and have Foo::A and Foo::B where Foo::B has `use Foo::A`? I guess that explains that
16:50 ugexe from what I got into it seemed like next-repo doesn't get set to the right thing somewhere
16:51 ugexe but that might just be a symptom
16:54 ugexe I assume it should technically get past that specific problem if I integrate it into rakudo (so it can short-id2cur etc) and re-compile?
16:56 ugexe I wonder if we can't expose that interface like RAKUDO_EXCEPTIONS_HANDLER
16:57 ugexe "If present, the print_exception routine will use a class of that name to process the exception for output. Rakudo currently ships with Exceptions::JSON (invoked by setting this variable to "JSON"), to override the default output."
17:29 ugexe Also CUR::Lib is to meant to proof of concept a Recommendation Manager as `method candidates` (mentioned in s22 as well, but not as a rec manager) https://github.com/ugexe/Perl6-CompUnit--Repository--Lib/blob/master/lib/CompUnit/Repository/Lib.pm6#L74
17:30 ugexe in CURI such a method would be like .resolve except that it considers the current repo only, and it returns all matches
17:31 ugexe (and thus .resolve and others would use this underneath)
17:34 ugexe this could allow the rec manager to be changed by the user for CURs, but thats not the real point. Rather it allows zef to use the same rec manager roles as the CURs to resolve
17:57 lizmat joined #perl6-toolchain
18:50 ugexe which I think might become more important if superceded-by, emulates, etc are implemented
19:21 lizmat joined #perl6-toolchain
20:36 llfourn joined #perl6-toolchain
21:20 nine ugexe: Yes. Ironically your struggles show me that mine with keeping CompUnit::Repository::Staging out of core were not in vain. I could have easily put it into the setting and be done with it, but it was a good test bed for custom repo implementations.
21:21 nine Unfortunately while I got it working well enough for packaging rakudo, it's still too fragile. But I'll have another look once I got require working well again.
21:37 llfourn joined #perl6-toolchain
22:36 llfourn joined #perl6-toolchain
23:37 llfourn joined #perl6-toolchain

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