Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-03-01

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

All times shown according to UTC.

Time Nick Message
06:06 llfourn joined #perl6-toolchain
07:05 domidumont joined #perl6-toolchain
07:08 domidumont joined #perl6-toolchain
07:45 nine_ mst: actually I punted the hardest question on what to actually allow in DependencySpecifications. I just write $spec.perl into the .deps file and EVAL it later. I just figured it will be a lot easier to test ideas for serialization formats against a working reference implementation.
08:19 TimToady joined #perl6-toolchain
09:19 El_Che it is OK to add additional information to the META6.json file? Maybe "namespaced" prefix_something: "blah"
09:25 lizmat In my mind it is, as the set that is used for installation is the "required" set only
10:35 JimmyZ_ joined #perl6-toolchain
10:48 El_Che thx
11:54 nine_ The Perl 5 toolchain gang has a discussion about META files and that they do contain much information that's not necessary for installation. Particularly there are issues with Unicode characters in author names and some tools that do not cope too well with that.
11:55 nine_ Maybe our takeaway from this is, that there will be non-Perl6 tools that want to read and process our META files and we always should keep them in mind.
11:55 nine_ Particularily worrying is that our META files are completely unversioned.
12:06 llfourn +1 for the possibililty of versioning META files like we version the spec
12:08 llfourn maybe we could make a JSON schema http://json-schema.org/ as part of the spec?
13:06 sufrostico joined #perl6-toolchain
13:10 z8 joined #perl6-toolchain
15:18 sufrostico joined #perl6-toolchain
15:35 ugexe perl5 already versions their meta
15:36 ugexe they use meta-spec 2 right now i believe
15:37 ugexe any meta keys you have in your meta will get installed, not just the subset it knows about. i attach arbitrary meta information that may be used later this way
15:56 ugexe it would probably be best if there was a specified field for such things though
15:57 ugexe that way a 3rd party CUR can make more assumptions about any keys it may want to add to the META6 format it understands
16:02 hoelzro joined #perl6-toolchain
16:24 hankache joined #perl6-toolchain
16:25 xdg Perl 5 META files aren't installed by default, so don't draw any conclusions.  Spec allows "x_" for any custom keys and those are widely used e.g. "x_contributors"
16:26 xdg Requiring "x_" insulates the spec from future collisions, but we then have a situation where tools will need to support "x_foo" even if "foo" becomes an official key.
16:27 xdg So, possibly, "x_" is an antipattern.  But then you have to lock things down or let it be the Wild West.
17:01 sufrostico joined #perl6-toolchain
18:06 Kassandry joined #perl6-toolchain
18:29 domidumont joined #perl6-toolchain
18:34 sufrostico joined #perl6-toolchain
18:48 llfourn joined #perl6-toolchain
18:48 mst nine_: eh, if that's working, I'm ok with it. it has the nice advantage that at some point we can yank that data from an installation of 'every module we can find' and that tells us what people are actually using and *then* we can figure it out from there
19:06 ilbot3 joined #perl6-toolchain
19:06 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
19:31 flussence joined #perl6-toolchain
23:41 lizmat joined #perl6-toolchain
23:41 ugexe joined #perl6-toolchain

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