Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-08-29

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

All times shown according to UTC.

Time Nick Message
06:41 domidumont joined #perl6-toolchain
06:46 domidumont joined #perl6-toolchain
08:19 leont joined #perl6-toolchain
10:56 leont joined #perl6-toolchain
11:46 tbrowder joined #perl6-toolchain
11:47 tbrowder hi, anyone here?
11:49 tbrowder questions about developing a module for distribution:
11:49 DrForr Here, but still recovering from YAPC :)
11:50 tbrowder 1. how does one identify the files and dirs to be installed? META6? Build.pm?
11:50 tbrowder I hear good things about YAPC!
11:51 tbrowder 2. where is definitive source for the contents of the META6 file?
11:52 moritz META6
11:53 moritz https://docs.perl6.org/language/modules#Distributing_Modules has some docs. It' probably not "the definitive source", but the best I know of
11:56 tbrowder yes, that doesn't help a lot; jnthn's meta6 test talks about allowable and not allowable but it's not clear to me yet how to find the detailed specification (but i haven't checked synopses, either)
11:57 tbrowder i just asked jnthn on #perl6
13:37 domidumont joined #perl6-toolchain
13:54 ugexe You can't identify which files and dirs to install
13:54 ugexe you can identify which modules to install via provides. you can identify which resources via resources. Anything in bin/ gets installed
13:55 ugexe S22 is the most definite source on META6 format but even that isn't set in stone
14:21 tadzik joined #perl6-toolchain
14:30 domidumont joined #perl6-toolchain
15:35 mst tadzik: hrm. now I'm wondering how many people using rakudobrew are, at this point, using it for anything except "installing and upgrading one moarvm based rakudo"
15:36 tadzik infinitesimal amounts, I think
15:36 ugexe i use rakudobrew to manage the various releases. so i have 2016.01, 2016.02, etc
15:43 moritz mst: I use it for upgrading, and having the option to roll back
15:43 mst moritz: yeah
15:44 moritz but it was more relevant back when we had several working and interesting backends
15:44 mst I do hope the JVM backend comes back eventually
15:44 mst but what I'm mostly thinking is "for people who don't already have a local::lib, what's the simplest thing we could provide that would be useful"
16:52 lizmat joined #perl6-toolchain
17:21 nine For building Inline::Perl5 we'd need $*VM.config variables, mapping logical library names to physical ones ($*VM.platform-library-name) and a way to capture output of command line tools into variables.
17:24 nine Kind of like: "build": {"makefile-variables": {"p5helper": {"library": "p5helper"}, "perlopts": {"run": "perl -MExtUtils::Embed -e ccopts -e ldopts"}}}
17:25 nine "library" would expand the name using: 'resources'.IO.child('libraries').child($*VM.platform-library-name($value.IO))
17:25 nine "run" just run($value, :out).out.lines.join('')
17:37 domidumont joined #perl6-toolchain
17:54 nine Aaaand that works
17:56 nine I guess we should ship this code as Distribution::Builder or something like that
18:12 nine rakudo/raccoon: b5a0394 | niner++ | / (3 files):
18:12 nine rakudo/raccoon: First steps towards a declarative build system for modules
18:13 nine rakudo/raccoon: review: https://github.com/rakudo/rakudo/commit/b5a03942d4
18:13 nine rakudo/raccoon: 979215d | niner++ | tools/ (4 files):
18:13 nine rakudo/raccoon: Install raccoon formerly known as install-dist.pl
18:13 nine rakudo/raccoon: review: https://github.com/rakudo/rakudo/commit/979215dd95
18:13 nine ugexe, mst: ^^^
18:51 mst oooo
19:07 nine Actually, since all native libraries will already be listed in resources, we could just as well create Makefile variables for them automatically without repeating them in the build section
19:44 ugexe https://github.com/rakudo/rakudo/commit/b5a03942d4d740033a0c19edf8b80f76ea3de47e#diff-e21a1dd06ec87bd9de6494e179d3386bR48 # Doesnt this add a dependency on perl 5?
19:47 nine ugexe: oops...that should be run($value).out.lines.join('')
19:48 nine pushed fixed commits
19:49 nine https://github.com/rakudo/rakudo/commit/acc13c67709338bd8c116fcf09a295fdb4adaef3
19:50 [Coke] ... did you just force push?
19:50 nine yes
19:51 [Coke] I was under the impression that we were supposed to never. ever. do that.
19:52 [Coke] maybe that's just for 'nom', but I thought it was more generic.
19:56 nine It's for branches that others work on which I'm quite sure is not yet the case here.
20:05 mst [Coke]: if it's your own branch and nobody else is going to have a problem, better to keep history clean
20:05 mst generally, I go for "don't force push unless there are no other people working on the branch who would have problems with this"
20:06 mst (I often force push on shared branches, but only when working with people who also prefer the trade-offs)
20:11 [Coke] sure, all fine. we should write down the policy.
20:11 mst my version mostly boils down to "screw dogma, just don't shit on other people"
20:11 [Coke] (in the same doc where we try to apologize for using 'nom' instead of 'master')
20:11 [Coke] mst: sure, that's fine. we should write that down
20:12 mst sure, I just don't think my phrasing is the correct one to put into the repo ;)
20:40 leont joined #perl6-toolchain
21:42 leont joined #perl6-toolchain
22:09 leont joined #perl6-toolchain
23:00 leont joined #perl6-toolchain

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