Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2017-07-12

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

All times shown according to UTC.

Time Nick Message
01:49 ilbot3 joined #perl6-toolchain
01:49 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:53 domidumont joined #perl6-toolchain
06:55 domidumont joined #perl6-toolchain
07:10 domidumont joined #perl6-toolchain
07:12 sjn joined #perl6-toolchain
09:11 sjn joined #perl6-toolchain
09:34 sjn joined #perl6-toolchain
09:38 domidumont joined #perl6-toolchain
09:56 domidumont1 joined #perl6-toolchain
12:13 domidumont joined #perl6-toolchain
12:23 domidumont1 joined #perl6-toolchain
12:27 domidumont joined #perl6-toolchain
12:59 awwaiid joined #perl6-toolchain
12:59 domidumont1 joined #perl6-toolchain
15:38 sjn joined #perl6-toolchain
16:39 stmuk_ what's the status of zef's support for modules with the same name?
16:52 ugexe i dont think zef has ever *not* supported that :)
16:53 ugexe when it comes to that the problem would be whatever ecosystem data is used
16:57 ugexe the first mirror tried for p6c is *not* my mirror (which should handle multiple copies of Foo) but the ecosystem-api one. mostly just because it updates more often
16:59 ugexe but you could even do something like create your own R* ecosystem: create an array of hash json where each hash is the meta data of a distribution. you can then put the git-commit id in the source url ala "source-url" : "https://github.com/author/repo.git@ajhuahef"
17:01 ugexe https://github.com/ugexe/zef/issues/142#issuecomment-287104151 (this explains how to edit zef config to understand such a new ecosystem)
17:24 domidumont joined #perl6-toolchain
17:40 ugexe nine: so should we try and remove the class Distribution workaround next (next) release or at 6.d?
17:41 ugexe from what i remember the only reason it was kept around was because of a roast test of `Distribution.new(:name<...>)`
20:12 nine ugexe: you're right, that's the only mention.
20:14 nine ugexe: I guess it's a question of how much pain it causes? With 6.d slowly becoming more real we may survive the wait
20:21 nine ugexe: panda does actually still use Distribution.new(...)
20:21 nine $to.install(
20:21 nine Distribution.new(|$bone.metainfo),
20:24 nine And panda actually still works mostly. It doesn't have CPAN support, so it won't install Inline::Perl5 for example, but it could still have some users.
22:32 perlpilot joined #perl6-toolchain
22:35 llfourn joined #perl6-toolchain
22:35 ranguard joined #perl6-toolchain

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