Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-02-07

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

All times shown according to UTC.

Time Nick Message
07:17 ilbot3 joined #perl6-toolchain
07:17 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
09:13 nine ugexe: I actually think we should just check for existence and die loudly (yet with an explanation) if the META6.json is invalid, i.e. is a directory, has no contents or just has invalid contents.
09:23 nine When something called META6.json is there, we have to assume that the user meant for it to be used, so informing her of a problem would be the prudent thing to do.
09:24 nine And as we've seen, we're not good at anticipating all the valid ways of providing a META6.json. For example it could even be a named pipe that doesn't have a size, but will supply us with valid meta data.
09:27 nine Sounds a bit contrived, but who knows what the crazy people in the Perl community come up with? Might just be some test setup. Even tests for CURI itself.
09:41 cognominal joined #perl6-toolchain
16:16 ugexe sure, but this issue is related specifically to symlinks (which serve the same purpose, and work fine on linux and osx in this regard)
16:17 ugexe point being: it should act the same on every OS due to the "automatically loads your META6.json" nature of ::FileSystem
16:18 ugexe on windows a symlink named META6.json pointing to a valid META.info that is cloned from git will be a valid file existing as META6.json but only contain the string "META.info"
16:20 ugexe dying loudly is fine (what happens currently). differing behavior by OS is not
16:32 ugexe let me be clear though: i am all for ramping up the strictness on all this stuff
16:33 ugexe ignore meta.info all together, make required meta fields actually required, etc
16:37 ugexe and make auth a specific required field to make it easier to search for (instead of having to search auth, author, and authority to find which one it came from)
16:41 ugexe for the sake of parsing a URN (like cpan:AUTHOR:Module-XXX:1.0) it also helps if auth requires a delimiter (':'), or instead have 2 required fields (content storage: cpan, owner: AUTHOR)
16:47 ugexe this all boils down to being able to know what meta fields to search for given only a modules full identity
16:48 sufrostico joined #perl6-toolchain
17:02 Cheery joined #perl6-toolchain
17:13 nine I think we share a pretty similar idea of how the goal looks like :) It's just the way there that's foggy for me
17:14 nine And by that I mean a deployable way mostly. The coding seems pretty straight forward
17:17 FROGGS joined #perl6-toolchain
17:43 sevvie joined #perl6-toolchain
19:40 hankache joined #perl6-toolchain

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