Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2015-02-23

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

All times shown according to UTC.

Time Nick Message
02:45 klapperl joined #metacpan
03:22 moltar joined #metacpan
03:39 moltar joined #metacpan
04:54 mauke_ joined #metacpan
07:30 neilb joined #metacpan
08:05 oiami joined #metacpan
08:07 oiami1 joined #metacpan
08:53 neilb joined #metacpan
09:07 neilb joined #metacpan
09:10 neilb_ joined #metacpan
09:30 neilb joined #metacpan
13:45 moltar joined #metacpan
14:23 Anon021 joined #metacpan
14:36 csson joined #metacpan
17:01 oalders neilb: i think the ++ data is being calculate in 2 different ways.  there are some open issues for it
17:02 neilb I thought it might be something like that. Interestingly I’ve spotted a couple of dists with this mismatch, but they were all “off-by-one” and they all had perlancar and sharyanto ++’ing them. Which made me wonder if it’s a caching thing as well, and things will “catch up”
17:03 neilb And indeed, the example I gave yesterday, or wheneber it was, is now right.
17:14 vroom joined #metacpan
17:16 moltar joined #metacpan
17:33 tianon joined #metacpan
17:50 punter joined #metacpan
18:39 punter joined #metacpan
18:54 neilb joined #metacpan
19:48 oalders https://metacpan.org/pod/README
19:55 ether ! how did that happen?
19:56 ether I see that dist contains a README.pod, but not README
19:57 ether $repo_root/README.pod is bad - it gets installed into @dist_name[0..-2]
19:57 ether i.e. for Git-Hooks, it will be installed into lib/Git/README.pod
19:57 alh Apparently common! https://metacpan.org/pod/Tutorial etc
19:58 haarg i'm guessing those things aren't in 02packages
20:00 ether I don't see any inappropriate m/README/ in 02packages
20:06 oalders https://metacpan.org/pod/Changes
20:08 ether wow
20:09 ether these are all from uploads only a few days old
20:10 trs ether: presumably they just swap around as new uploads come up
20:10 trs the /pod endpoint is rather liberal at trying to get what you asked for, IIRC.
20:11 trs and it's not always what a human might expect if given something that's not a package name
20:11 trs /pod/cpanm isn't always App::cpanminus' cpanm, for example.
20:11 trs depending on what was uploaded last.
20:12 trs see also: https://github.com/CPAN-API/cpan-api/issues/373
20:12 BinGOs metacpan's "I feel lucky" endpoint
20:12 trs :)
20:12 alh Heh
20:14 BinGOs if I was feeling more motivated I would exploit this feature for lulz
20:18 haarg see also http://api.metacpan.org/
20:20 reneeb joined #metacpan
20:31 metacpan joined #metacpan
20:31 metacpan [metacpan-web] ranguard pushed 2 new commits to master: http://git.io/Aiz9
20:31 metacpan metacpan-web/master 2525153 Dave Cross: Fix links in news feed.
20:31 metacpan metacpan-web/master 451aeaf Leo Lapworth: Merge pull request #1462 from davorg/master...
20:31 metacpan left #metacpan
20:50 mjgardner joined #metacpan
20:54 mjgardner Hi, trying to start hacking on an API issue, got my VM set up OK but am stuck on the step in metacpan-developer/README_API.md where one loads a CPAN mirror. cpan -P fails with this: http://cl.ly/Zud5
20:55 mjgardner Oh foo, that is badly formatted.
20:56 mjgardner Here: https://gist.github.com/mjgardner/88488ff506b34ff3882b
21:11 ranguard rwstauner: ^^
21:11 ranguard oalders: ^^ ?
21:11 oalders checking
21:12 oalders i don't think you actually need to follow that step
21:12 oalders there's a script that will sync a partial CPAN for you
21:13 oalders ugh. maybe it got removed from the docs
21:16 oalders oh, it is still there.  just kind of buried: "sh /vagrant/bin/index-cpan.sh"
21:16 oalders mjgardner: any reason you need all of CPAN?
21:17 oalders for your purposes i would think a partial mirror would be fine.
21:17 mjgardner Probably not, just doing it to be thorough.
21:17 oalders you could just blacklist an arbitrary dist to test on
21:17 oalders thorough is good, but in this case it'll really kill your VM resources if you have to index it all
21:18 mjgardner OK
21:18 oalders if you blacklist a dist which has some previous releases and some after it, that should be enough to ensure that your changes don't blow away all releases for the same dist
21:19 oalders blacklist a *release*
21:19 oalders sorry
21:21 punter joined #metacpan
21:22 ranguard oalders: ^^ please document that :) - or make the docs clearer if it is already :)
21:23 oalders Yeah, it's in there.  I'll make it more obvious. :)
21:52 moltar joined #metacpan
22:52 vroom joined #metacpan
23:03 mjgardner joined #metacpan
23:57 vroom joined #metacpan

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