Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2015-08-27

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

All times shown according to UTC.

Time Nick Message
02:37 melo joined #metacpan
08:00 oiami joined #metacpan
08:09 Relequestual joined #metacpan
08:24 margeas joined #metacpan
10:51 margeas joined #metacpan
11:18 pjfl joined #metacpan
11:25 oiami joined #metacpan
13:02 margeas joined #metacpan
13:04 jdv79 joined #metacpan
13:04 jdv79 has there been any talk of p6 support?
13:04 jdv79 hello, btw
13:08 haarg not that i'm aware of
13:09 haarg it would depend a lot of how cpan/pause handled it
13:11 jdv79 well, not much has been done on it and i am about to patch a bug in the current handling
13:12 jdv79 currently pause will detect a META6.json file and insert a Perl6 subdir under the username portion of the cpan path
13:12 jdv79 that's pretty much it, so far
13:13 jdv79 i'm interested in exploring if its worth trying to use parts of the p5 ecosystem so p6 doesn't have to reinvent everything now, if at all.
13:15 jdv79 so for example, right now i have a p5 dist at http://www.cpan.org/authors/id/J/JD/JDV/Data-Selector-1.00.tar.gz and, once this bug in pause is addressed, i will also have a p6 dist at http://www.cpan.org/authors/id/J/JD/JDV/Perl6/Data-Selector-1.00.tar.gz
13:16 haarg how are p6 dists packaged?
13:17 jdv79 so, now sure if we could mix p5 and p6 dists in the same results or would they have to be seperated (different api/site somehow- path/host...)
13:17 jdv79 so far very similarly to p5
13:17 jdv79 t, lib, bin,... and the META6.json file is the differentiator atm
13:18 jdv79 just wondering if the way we've decided to handle p6 dists at pause/cpan is best for the more important downstream uses
13:19 jdv79 like testers, metacpan, maybe p5 pkg mgrs, idk...
13:20 jdv79 *not
13:21 vroom joined #metacpan
13:54 TBSliver joined #metacpan
13:57 oalders jdv79: is there an open issue for the PAUSE bug?
13:58 oalders will the p6 modules be listed in 02packages?
14:11 jdv79 oalders: no
14:11 jdv79 i am preparing/testing a PR though
14:11 jdv79 i should log a bug i guess
14:11 jdv79 the indexes will be separate and have yet to be determined:)
14:11 oalders that makes sense
14:12 oalders jdv79: basically, if it's something we can support (p6) we'd need someone to take on that project
14:13 oalders so basically "patches welcome", i guess. we'd have to figure it out internally to see how disruptive it might be
14:14 jdv79 i'm looking for guidance from the domain experts
14:14 jdv79 as we are now trying to flesh out the pause/cpan part and don't have a lot of experience with the consumers
14:14 jdv79 or i don't:)
14:16 oalders jdv79: you could look at https://github.com/CPAN-API/cpan-api/
14:16 oalders maybe start with https://github.com/CPAN-API/cpan-api/blob/master/lib/MetaCPAN/Model/Release.pm
14:16 jdv79 k
14:17 oalders basically the tools need to be in place to unpack the dist, extract the stuff we need, parse out docs, etc
14:18 oalders and i imagine it would require a new Elasticsearch index rather than sharing the current one
14:20 jdv79 hmm...
14:21 jdv79 ok
14:21 jdv79 no way to piggyback or anything for search?
14:23 haarg it doesn't sound very useful to have a combined index
14:24 dolmen joined #metacpan
14:25 vroom joined #metacpan
14:27 jdv79 probably not.  just trying to do the least amount of owrk necessary
14:28 haarg trying too hard to fit into the existing tools will only create more work later for both sides
14:33 jdv79 yeah.  probably.
14:33 jdv79 some of the peeps want to do it all in p6
14:34 jdv79 we'll see
14:34 vroom joined #metacpan
14:42 jdv79 oalders: https://github.com/andk/pause/issues/182 - finally got it done; hopefully
14:43 oalders jdv79: thanks. am watching that ticket
14:51 melo joined #metacpan
15:19 vroom joined #metacpan
15:23 neilb joined #metacpan
15:23 vroom joined #metacpan
15:32 vroom joined #metacpan
15:39 oiami joined #metacpan
16:39 neilb joined #metacpan
16:46 neilb_ joined #metacpan
17:09 ribasushi joined #metacpan
17:43 Peter joined #metacpan
17:59 ranguard jdv79: seems mad to reinvent the wheel
18:00 ranguard but agree that it should be a seperate index in ES
18:08 vroom1 joined #metacpan
18:10 vroom2 joined #metacpan
18:32 neilb_ joined #metacpan
18:47 Peter joined #metacpan
19:02 vroom joined #metacpan
19:10 vroom1 joined #metacpan
19:12 jdv79 ranguard: yeah
19:15 ranguard jdv79: Perl6 does need a CPAN though, the current 'install via git[hub]' thing is so weak (it's what other languages do!)
19:15 * ranguard just knew he wasn't going to be the one to do it ;)
19:16 jdv79 i would be more ok with it if it used fixed points in time for versions instead of just HEAD
19:16 jdv79 its kinda ridiculous now but "it works" and i imagine it was easier to setup at first
19:17 ether IMHO there should be a separate metacp6an.org site, which forked off the metacpan code
19:17 ether I don't think perl6 code belongs on the same site as perl5
19:18 jdv79 sure
19:18 ether and if it was implemented in perl6, you'd definitely need to fork anyway :)
19:18 jdv79 well, that's the thing.  people want to write everything from scratch
19:18 jdv79 but in reality that's not really practical given the p6 commmunity is like tens of people
19:19 jdv79 so its possible p6 will use the p5 stuff to bootstrap and bounce later or it might just stick around
19:19 jdv79 who knows what will happen though
19:20 * ranguard isn't going near p6 until there is a CPAN/PAUSE equiv
19:20 jdv79 for instance the build processes, various utils, prove - p6 still uses p6 for all of that:)
19:20 oalders meta6pan.org
19:20 jdv79 good stuff!
19:20 oalders jdv79: it really is a pile of work to reinvent metacpan
19:20 oalders the first 80% is easy, though ;)
19:20 jdv79 metacp6an.org?
19:21 jdv79 its a pile of work to rewrite a bunch of stuff; pretty much always:)
19:21 ranguard oalders: so we're at 82% right :) ?
19:21 oalders :D
19:21 jdv79 so why not not do that and do something interesting
19:21 jdv79 haha
19:21 jdv79 basically my thoughts in a nutshell
19:21 oalders judging by the number of open tickets we're not even close to being done
19:22 oalders plus, you have uptime to worry about
19:22 jdv79 not that metapcan isn't interesting - but its done and likely easily adapted
19:22 oalders we have a bunch of people who can poke at metacpan if things go wrong, but it took years to get to this point
19:22 ranguard jdv79: we've got the hardware, world wide CDN (Fastly) and code base, if you have the time
19:23 jdv79 good to know. thanks
19:23 ranguard jdv79: oh, yea, and the puppet config
19:23 ranguard and the Dev vm
19:23 ranguard and the irc channel
19:23 oalders and we also have ranguard
19:23 ranguard just not the development resources
19:24 jdv79 i'm hoping that unlike pause getting metacpan running locally on my laptop doesn't take hours
19:24 jdv79 ugh.  that was a chore i would settel for never doing again.
19:24 ranguard jdv79: full stack, or just web front end?
19:24 jdv79 full stack
19:24 ranguard jdv79: https://github.com/CPAN-API/metacpan-developer - there's a VM for it
19:26 vroom joined #metacpan
19:28 ranguard it _should_ just work, though has been a whilst since anyone new tried running it
19:28 jdv79 oh, nice
19:28 ranguard do open issues / send updates on the docs if you get stuck
19:28 jdv79 and btw, once that issue i found gets resolved and the indexer gets firmed up there will be a cpan and pause
19:29 jdv79 basically the cpan and pause:)
19:29 oalders :)
19:29 ranguard as long as that's adopted... SWEEET :)
19:29 jdv79 there is an indexer right now but i'm not sure its good enough yet
19:29 oalders jdv79: let us know if you run into any problems with the VM
19:29 jdv79 ok
19:31 jdv79 looks like the current indexer inserts into the p6(dists,provides,binaries) tables and they are spewed out into *.json daily.  idk about that.
19:32 jdv79 the 3 files at the bottom of http://www.cpan.org/authors/ is what i meant
19:32 jdv79 anyway.  we'll see.  there seems to be a lack of concensus or interest in this area atm:(
19:33 ranguard jdv79: good luck, hope you manage to find a big enough clue stick to hit people with
19:53 Peter joined #metacpan
20:41 grantm joined #metacpan
21:06 margeas joined #metacpan
23:56 metacpan joined #metacpan
23:56 metacpan [metacpan-web] rwstauner created profile-extra-json (+2 new commits): http://git.io/vGIwB
23:56 metacpan metacpan-web/profile-extra-json 6dc5c9d Randy Stauner: Don't utf8-decode params if Catalyst has already done it
23:56 metacpan metacpan-web/profile-extra-json 15e06bd Randy Stauner: Leave template view json as a character string...
23:56 metacpan left #metacpan
23:56 metacpan joined #metacpan
23:56 metacpan [metacpan-web] rwstauner pushed 1 new commit to master: http://git.io/vGIww
23:56 metacpan metacpan-web/master 309025a Randy Stauner: Remove Data::Dumper load
23:56 metacpan left #metacpan
23:59 vroom joined #metacpan

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