Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-release, 2016-01-24

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
13:07 FROGGS joined #perl6-release
13:52 FROGGS_ joined #perl6-release
16:39 jnthn nine: Was that branch made by cherry-pick, ooc?
16:42 * jnthn figures so
16:42 jnthn I suggest 770d1097 and 5a04ff6ab be picked also
16:42 jnthn One is a harmless typo fix, the other a nasty Supply.grep bug fix
16:44 nine jnthn: yes, I cherry-picked
16:44 jnthn OK, mind if I cherry pick those two also?
16:45 jnthn I looked over what's in there and it seemed reasonable to me.
16:47 nine Oh please do :)
16:48 jnthn Done.
16:48 jnthn Builds fine on Windows, btw
16:48 jnthn Are we happy we can make an R* out of what's in this branch?
16:49 nine I vote yes
16:52 * jnthn also spectests on Windows against 6.c
16:53 jnthn Will then use it to try and install a panda and some modules
16:53 jnthn I've started work on a compat/versioning guidelines doc, fwiw.
16:53 nine This will be the first release that doesn't contain new features. What better base for a R*? :)
16:54 jnthn :)
16:54 nine Sounds great :)
16:54 jnthn I basically was too exhausted in the first half of January to do much of anything, though, so last week and this week am taking care of various $dayjob things. I'll have more time again in Feb. :)
16:55 jnthn But if I can get a draft of the guidelines that I'm happy with out during the next few days I'll do so.
16:58 nine I can sympathize...the couple of days vacation I just had really did not come too soon :)
16:59 jnthn :)
16:59 jnthn Hope it was fun
17:01 nine I'd do it again even knowing I'd end up with the bruised rib, so yes :)
17:02 jnthn Ouch...but nice :)
17:03 jnthn Well, the panda install on Windows from that branch went well
17:03 jnthn I've just need told it's time to cook paneer achari :)
17:03 nine Sounds delicious, so go for it!
17:09 jnthn OO::Monitors installed just fine on Windows with panda
17:09 jnthn spectest isn't a source of concern
17:09 jnthn So looking decent from here
17:09 jnthn Provided it's R*-able I'm happy enough with this
17:09 jnthn OK, really cooking :)
18:28 FROGGS_ it is probably not R*able out of the box, since star requires a (not committed) rakudopatch and pandapatch
18:34 lizmat joined #perl6-release
18:35 jnthn FROGGS_: Can we get that rakudopatch into 2016.01 prep branch, please?
18:36 jnthn Or better, into the nom branch, and then apply the pandapatch to go with it, and then cherry-pick to 2016.01-preparation
18:39 nine I wonder what those patches are about
18:43 FROGGS_ nine: look at the two patches here: https://github.com/rakudo/star/tree/release
18:49 jnthn Ah, patches in https://github.com/rakudo/star/commit/27046e33e9fd9c6bd3e5cdcc180f42b15562f6d1 ?
18:50 FROGGS_ https://github.com/rakudo/star/blob/release/panda-bindir.patch
18:50 FROGGS_ https://github.com/rakudo/star/blob/release/rakudo-cur-bindir.patch
19:17 nine Why do you need to supply a different bin-dir?
19:30 FROGGS_ nine: because install/bin of a star installation will end up in PATH
19:31 FROGGS_ not install/share/perl6/site/bin
19:50 stmuk I sort of wish rakudo did that by default
19:50 stmuk two PATH entries are annoyng
20:14 jnthn What's the distribution (as in, Linux distribution) perspective on it, if anyone knows?
20:14 jnthn It'd be easier for me on Windows if they ended up in the same bin.
20:18 * jnthn going to rest; back tomorrow &
20:18 FROGGS_ there is only one bin dir on linux too thar's used for e.g. a programming lauage
20:19 jnthn Well, I suspect Node's npm goes parallel on installation to nodejs itself, for example.
20:19 jnthn So it'd make sense to install panda in such a way
20:21 jnthn Anyways, really gone for now :) &
20:21 FROGGS_ sleep well

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary