Camelia, the Perl 6 bug

IRC log for #metacpan, 2013-08-29

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

All times shown according to UTC.

Time Nick Message
00:54 shmuel joined #metacpan
01:16 klapperl joined #metacpan
01:48 Al3xG0 joined #metacpan
01:50 shadowpaste "al3xg0" at 217.168.150.38 pasted "windows x64" (1 line) at http://paste.scsys.co.uk/266932
01:50 dipsy [ magnet_web paste from "al3xg0" at 217.168.150.38... ]
01:52 Al3xG0 left #metacpan
03:13 mauke_ joined #metacpan
03:14 preflex_ joined #metacpan
05:44 ether_ joined #metacpan
06:10 dam joined #metacpan
06:12 dam ranguard: https://metacpan.org/release/Clone-Fast is 404, while http://search.cpan.org/dist/Clone-Fast/ is OK (and you wanted to know of any potential problems :) )
06:12 dipsy [ Joshua ben Jore / Clone-Fast - search.cpan.org ]
06:19 kentaro joined #metacpan
06:30 dpetrov_ joined #metacpan
07:01 SineSwiper joined #metacpan
07:45 ranguard dam: I did? - oh as to why people use s.c.o - sure
07:45 ranguard dam: a ticket for that would be good :)
07:57 haarg it's not in 02packages
08:28 dam so it *is* removed from CPAN and s.c.o showing it is a bug?
08:35 daxim joined #metacpan
08:46 ranguard dam: yep
08:46 ranguard well, bug/design decision
09:51 daemon joined #metacpan
10:12 shmuel_ joined #metacpan
12:30 bowtie_ joined #metacpan
13:57 alh joined #metacpan
15:49 oalders haarg: could you include me in the conversation about the necessary changes for MetaCPAN::API?
15:50 oalders was going to bring that up, but i saw you were discussing with sawyer
15:50 dam ranguard: I see. thanks for the clue!
16:01 haarg oalders: the idea was less 'changes' and more 'start over', although with some backwards compatible bits where reasonable
16:02 oalders haarg: that sounds good. i just wouldn't mind seeing what's planned, if possible
16:03 oalders i'd like to be able to push more people in the direction of MetaCPAN::API
16:03 oalders right not that's a bit tough as it's quite limited
16:14 haarg oalders: i didn't have any luck finding what i had written down, but here's the concept for the API: http://gist.github.com/6380159
16:14 dipsy [ metacpan-api.txt ]
16:28 dam left #metacpan
16:34 oalders haarg: that looks good.  using ElasticSearch.pm under the hood would be key.  or even ElasticSearchX::Model
16:55 * mst still thinks pretending that exposing your back end to the world is an API rather than just a pair of buttocks was a strategic error, but oh well
17:00 klapperl_ joined #metacpan
17:45 oalders well, if this project had involved writing an actual API it may never have been done
17:45 oalders or we'd just be arguing about how bad it is and who thought this was a good idea anyway
17:45 rwstauner :-)
17:46 rwstauner oalders++ # realistic
17:46 oalders :)
17:46 oalders the fact that ES does the grunt work out of the box was one big reason we chose it
17:46 oalders and it takes a lot of arguments out of the equation
17:47 rwstauner elasticsearch++ # bonsai cool
17:47 oalders :)
21:24 Khisanth joined #metacpan
22:36 meraxes joined #metacpan
22:49 rwstauner joined #metacpan
22:49 rwstauner joined #metacpan
22:56 meraxes joined #metacpan
23:03 meraxes joined #metacpan
23:33 dsteinbrunner joined #metacpan

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