Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2016-09-28

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:30 ronsavage JK: I'm on the CPANTesters emailing list, so I've asked for help.
00:43 iarna joined #marpa
00:51 ronsavage JK: Here's a reply:
00:51 ronsavage > There's no META.* files, which probably doesn't help... if the smoker is
00:51 ronsavage > taking shortcuts and expecting to find a META.* (which it shouldn't)
00:51 ronsavage > without running Makefile.PL, then that would explain why the smoke
00:51 ronsavage > report is reporting no prereqs at all.
01:07 ronsavage JK: More info:
01:07 ronsavage > META.json and META.yml are supposed to be included in the uploaded
01:07 ronsavage > tarball. They would be produced via 'perl Makefile.PL && make && make
01:07 ronsavage > test && make manifest && make dist'.
01:08 ronsavage Are you using that incantation to end in 'make dist'?
01:17 ronsavage JK: Your makefile reports (quotes are from emails) "Actually, it reports ExtUtils::MakeMaker (0) as a prereq."
01:18 ronsavage And:  " … and the MYMETA.json that's generated when I  run it here (yay insomnia!), specifies ExtUtils::MakeMaker (0) as the  only "build" prereq.
01:18 ronsavage Data::Dumper and a whole slew of other modules are specified as "configure" prereqs.
01:18 ronsavage Might it be that the smoker is for some or other reason (overwrite instead of merge?) seeing only the "build" prereqs?
01:18 ronsavage … though, shouldn't (most of?) those prereqs be "runtime" prereqs?"
01:18 ronsavage Sounds like you need to switch from my %version_for_config = (...) to something which generates build_requires.
01:31 idiosyncrat_ ronsavage: Thanks!
01:31 idiosyncrat_ I think you may have found the problem.
01:32 idiosyncrat_ There need to be META.* files in the tarball
01:32 idiosyncrat_ I'm surprised 5.10.1 is the only thing that broke.
01:32 idiosyncrat_ I'll fix this in the next release.
01:32 idiosyncrat_ Again, thanks, thanks, thanks.
01:48 ilbot3 joined #marpa
01:48 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Pastebin: http://scsys.co.uk:8002/marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today
03:01 ronsavage joined #marpa
04:36 JPGainsborough2 joined #marpa
07:12 ronsavage joined #marpa
07:45 sirdancealot joined #marpa
08:11 ronsavage joined #marpa
10:30 kaare_ joined #marpa
16:50 sirdancealot joined #marpa
17:32 VsyachePuz joined #marpa
19:14 maybekoo2 joined #marpa
20:21 sirdancealot joined #marpa
20:56 sirdancealot joined #marpa
22:28 ronsavage joined #marpa
22:39 ronsavage JK: Another email re the Makefile issue:
22:39 ronsavage The 'configure' step is when you run Makefile.PL. And because there's no META.yml, the only way to find out what the configure_requires modules are is to run Makefile.PL. By the time that has put the resulting data into Makefile it's too late to actually *use* that data.  Change the CONFIGURE_REQUIRES to BUILD_REQUIRES and CPAN clients should DTRT.
23:08 sirdancealot joined #marpa
23:21 idiosyncrat_ joined #marpa
23:24 ronsavage JK: More info: If those prereqs are needed at runtime, they belong in PREREQ_PM.  BUILD_REQUIRES is only for things needed at the "make" or "./Build"  step.

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary