Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-10-10

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

All times shown according to UTC.

Time Nick Message
01:11 tbrowder .tell ugexe it looks like the two good links are working, but i notice the link in the modules.perl6.org is to the head of the master branch, not to the latest release commit!
01:33 tbrowder .tell ugexe see latest issue i just submitted for ecosystem
01:48 ilbot3 joined #perl6-toolchain
01: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
04:55 stmuk joined #perl6-toolchain
05:41 domidumont joined #perl6-toolchain
05:47 domidumont joined #perl6-toolchain
06:14 domidumont joined #perl6-toolchain
06:39 domidumont joined #perl6-toolchain
12:39 perlpilot joined #perl6-toolchain
15:43 ugexe tbrowder: i'm not sure how fixable that is. it would have to take the META6.json url and determine if its linked to a specific commit - if so then store the dist url using the commit from the META6.json url
15:43 ugexe https://github.com/tbrowder/Net-IP-Lite-Perl6/blob/871537d12004fd8631df11fe20a9d89c1331b010/META6.json
15:43 ugexe https://github.com/tbrowder/Net-IP-Lite-Perl6/tree/871537d12004fd8631df11fe20a9d89c1331b010/
15:44 ugexe however
15:45 ugexe the reason I say I don't know how fixable that is is because that transformation only works for github
15:46 ugexe maybe bitbucket or gitlab use a slightly different url scheme. or maybe the META6.json isn't even hosted on a git provider at all
15:54 ugexe One solution may be to use the META6.json fields `"support" : { "source" : "https://github.com/user/repo/tree/092j3f0j2flj3f" }` to point your source at the specific commit and have modules.perl6.org use *that* as the distribution's linked url (and use the current behavior if that field does nto exist)
15:55 ugexe *puts referral urls in modules `source` field*
16:44 tbrowder okay, good thinking.  i'm ready to try that whenever you say. i assume, for the moment, that only the latest release referenced in the multiple meta files would be used? or do you need to tweak some code?
16:52 tbrowder oops, do we have chicken-and-egg situation referring to a commit before it happens?
16:54 FROGGS joined #perl6-toolchain
16:55 tbrowder no! just have the master meta have the desired source link, shouldn't that work?
17:46 domidumont joined #perl6-toolchain
21:42 ugexe it would need some (easy) tweaks yeah, but I wasn't volunteering. https://github.com/perl6/modules.perl6.org/tree/master/lib/ModulesPerl6 would be a good place to start looking if you're motivated enough
22:02 tbrowder well, i'm fairly motivated, and S22 could be modified to add new key-value pairs under the support hash. i'll take a look. i'm already working on a PR for Test::META so this seems a natural fit. thanks!
22:24 ugexe also remember s22 stuff is meant to be generic as possible. the various content storages will have their own api that consumers will need to understand. For instance: "source-url" is not s22 spec but a spec of the current perl6 ecosystem... cpan/metacpan use "download_url". s22 can't dictate how metacpan serves such a thing, so its up to the consumer to understand whatever interface is provided

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