Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2016-01-06

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

All times shown according to UTC.

Time Nick Message
00:23 vroom joined #metacpan
03:31 punter joined #metacpan
03:32 vroom joined #metacpan
04:06 punter joined #metacpan
08:00 oiami joined #metacpan
08:01 neilb joined #metacpan
08:51 neilb joined #metacpan
09:09 neilb joined #metacpan
10:42 punter joined #metacpan
13:23 Relequestual joined #metacpan
13:41 vroom joined #metacpan
15:45 jwang joined #metacpan
16:04 Khisanth joined #metacpan
17:37 neilb joined #metacpan
18:04 punter joined #metacpan
19:52 ether in what repository does the indexing code live? it's not metacpan-web, is it?
19:53 * ether found that META.* doesn't seem to be taken into consideration in the same way that PAUSE uses it, so indexing results can differ.
19:56 oiami joined #metacpan
19:59 ranguard ether: cpan-api repo
19:59 ether danke!
20:02 ranguard ether: https://github.com/CPAN-API/cpan-api/blob/master/lib/MetaCPAN/Script/Release.pm I _think_
20:04 ranguard Good place to start if nothing else
20:05 * ranguard really hates POD in the __END__
20:07 ether why?
20:07 ether it at least guarantees it can't be parsed as code
20:36 mst unless you have __DATA__ I don't honestly care much
20:47 * ranguard wants SOMETHING at the top so I can see what it's meant to do before I start scanning code
21:03 mst ah, so, I don't really use __END__
21:03 mst but I *do* pretty much always have the POD after the code

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