Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
Set by moderator on 10 February 2017.
00:47 llfourn joined 01:21 b2gills joined
[Coke] ranguard: what is the point of that page? 01:30
are you trying to make cpan releases or something?
shadow.cat/blog/matt-s-trout/the-ps...xperiment/ ? 01:35
01:48 llfourn joined 02:50 llfourn joined 03:51 llfourn joined 04:53 llfourn joined 05:54 llfourn joined 06:56 llfourn joined 07:57 llfourn joined 08:58 llfourn joined
ranguard [Coke]: I run PSIXDISTS code 09:52
I've just put the uploading into nightly cron, so was then looking at cleaning out the old uploads and realised how much somethings change, so I'll be uploading a LOT of that module 09:53
sorry, should have made that clear 09:54
10:00 llfourn joined 11:02 llfourn joined 12:03 llfourn joined 13:04 llfourn joined 13:36 awwaiid joined
nine ranguard: could you check the META6.json and only upload a dist if the version changed? 13:44
ranguard nine: could do.. but my understanding is authors forget to update that, so if someone wants the 'latest' from CPAN they might be waiting a long time 13:52
nine ranguard: we have to get better at updating version anyway. Our installers already refuse to update a module when the same version is already installed.
ranguard heh, so if I install Foo one week and you install the same version the next week we'll actually end up with different code... this isn't going to cause any issues ;) 13:54
if only people were using some sort of standardized release process where we could impliment checks :) 13:55
nine: my stuff is only ever meant to be sticky plaster until a real fix is found (techncal or social/community) 13:58
14:06 llfourn joined 15:07 llfourn joined 16:09 llfourn joined 17:14 llfourn joined 18:15 llfourn joined 19:17 llfourn joined 20:18 llfourn joined 20:58 ribasushi joined 21:19 llfourn joined 22:21 llfourn joined 23:23 llfourn joined