Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-12-27

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

All times shown according to UTC.

Time Nick Message
00:29 idiosyncrat joined #marpa
00:30 idiosyncrat Demat!
01:34 idiosyncrat amon: re travis
01:34 idiosyncrat I came across what is for me probably a better way to turn Travis builds on and off --
01:34 idiosyncrat there's an option to build only if there is a .travis.yml in the repo.  I've turned this on.
01:35 idiosyncrat If I don't want a build, I can "git mv .travis.yml .travis.yml.bak"
01:36 travis-ci joined #marpa
01:36 travis-ci jeffreykegler/Marpa--R3#15 (master - 7b0ff82 : Jeffrey Kegler): The build passed.
01:36 travis-ci Change view : https://github.com/jeffreykegler/Marpa--R3/compare/72556152a3a3...7b0ff82342b2
01:36 travis-ci Build details : https://travis-ci.org/jeffreykegler/Marpa--R3/builds/322013609
01:36 travis-ci left #marpa
01:37 idiosyncrat Looking at the docs, travis has facilities for deployments and uploads.  It might be useful for both R2 and R3 to have a kind of pre-CPAN deployment, so that I deploy Travis versions ...
01:38 idiosyncrat and once they look OK deploy on CPAN.
01:38 idiosyncrat This would mean, for R3, a lot fewer developer's releases.
01:39 idiosyncrat And on R2, it could mean more releases -- I could keep CPAN ultra-stable, but do Travis releases, and only do an R2 CPAN release when there is a real bug fix.
02:17 ronsavage joined #marpa
02:35 ronsavage JK: So where would these 'Travis deployments' appear?
02:56 ilbot3 joined #marpa
02:56 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Code paste/run: https://f.perlbot.pl/#marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today - Youtube channel: https://www.youtube.com/channel/UCYKVfGBtfTqbs1JdYq-dc5g
04:06 idiosyncrat ronsavage: Actually they *already* are appearing in https://github.com/jeffreykegler/Marpa--R3/releases
04:06 idiosyncrat So for example Marpa::R3 4.001_050 is available (right now) via URL https://github.com/jeffreykegler/Marpa--R3/archive/Marpa-R3-4.001_050.tar.gz
04:07 idiosyncrat cpanm I believe can install from these URL's
04:07 idiosyncrat And Travis can deploy to them.
04:08 idiosyncrat The one difference is that they would not be seen by CPANtesters.
04:47 ronsavage OK. So as I thought, they have dev versions #s......
04:49 ronsavage Hmm. I see you've made a lot of changes without changing the version #:
04:49 ronsavage -rw-r--r-- 1 ron ron 1149423 Nov  5 12:57 Marpa-R3-4.001_050.tar.gz
04:49 ronsavage -rw-r--r-- 1 ron ron 1515942 Dec 27 15:47 Marpa--R3-Marpa-R3-4.001_050.tar.gz
04:53 ronsavage And I see you ship about 25 makefiles of various sorts. The one in the root dir dies with Nothing to be done for 'dummy', whereas the one in cpan dies with *** No rule to make target 'read_only.time-stamp', needed by 'gnu_ac_build.time-stamp. Is there any point in my trying the make anything?
04:55 idiosyncrat I was, er, overlooking, some issues. :-)
04:55 idiosyncrat First, you don't need to try making anything, though that is what Travis & amon are doing at the moment.
04:56 idiosyncrat The one from github is a top-level tarball, and the one you pulled from CPAN is a CPAN tarball.
04:57 idiosyncrat Travis IIRC correctly allows me to configure so that I "release" CPAN tarballs on Github, instead of (or together with?) the top-level tarballs that are in the releases directory now.
04:58 idiosyncrat cpanm will, of course, only install CPAN tarballs.
04:59 idiosyncrat But note that the .travis.yml files contains instruction on how to build & test top-level tarball.
04:59 idiosyncrat I'd need to add an instruction to the .travis.yml telling it how to make the CPAN tarball.
05:29 ronsavage Gotcha! But, OK, it's not as important as development at your end :-). I await new (dev) versions.....
05:30 idiosyncrat When the 1st Travis github-based developer's build rolls out, I'll let you know specifically, as well as how it should be built.
05:31 idiosyncrat You'll probably get plenty of warning that it's coming, since in figuring out how to put it together, I'll be asking amon lots of questions on this channel. :-)
06:19 ronsavage joined #marpa
12:41 amon_ joined #marpa
12:43 amon_ Re Travis: I'm glad this turned out to be useful.
12:44 amon_ But turning Travis builds off by moving the .travis.yml file does not seem to be a good idea: that introduces lots of noise in diffs and for blame/annotate
12:45 amon_ I don't really see a good reason to suppress builds. You can always ignore the notification email.
12:46 amon_ The GH releases are by default just a snapshot of the repo when you push a tag.
12:47 amon_ It is not currently possible to install the Marpa repos or the GH releases with "cpanm https://github.com/..." because Marpa does not have a Buil.PL/Makefile.PL in the top level
12:49 amon_ But because there are frequent CPAN releases, this functionality isn't really needed. Uploading dev versions to CPAN seems like a very good idea.
12:50 amon_ In particular, Travis CI cannot compete with the breadth of CPAN Testers.
12:53 amon_ Uploading tarballs that GH should offer as a release download is possible, though I haven't done that previously. But does this really provide significant value over making installation of the source code directly possible?
12:54 amon_ (Also, I'm not an expert in anything. I'm just someone who occasionally reads the documentation.)
19:40 iarna joined #marpa
21:20 chansen_ joined #marpa
21:43 ceridwen joined #marpa
21:43 ceridwen joined #marpa
22:54 amon_ left #marpa
23:27 idiosyncrat joined #marpa

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