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 23 May 2017.
01:49 ilbot3 joined
moderator 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
05:34 domidumont joined 05:41 domidumont joined 06:12 domidumont joined 07:39 nine joined 07:40 camelia joined 07:48 camelia joined
tbrowder ugexe: can you list desired or recommended naming formats for releases to best work with current state of ecosystem/cpan mix? there is interest on #perl6 11:28
thanks 11:29
ugexe tbrowder: 1) if you setup your .gitignore properly the .tar.gz github will generate won't include files cpan probably doesn't want to host 2) you can name your release whatever you want (most people use v0.0.0 format) but if you name the release `My-Dist-v0.0.0` you can upload to cpan/pause by just giving it the github link to that release .tar.gz. Note that this will works if you *dont* rename your 14:15
release, but then you'd have to remember what all those `vx.x.x.tar.gz` files represent when you have multiple modules uploaded
e.g. you would get github.com/ugexe/zef/archive/zef-v0.1.15.tar.gz instead of github.com/ugexe/zef/archive/v0.1.15.tar.gz 14:16
ultimately the names don't matter. just the limitations of the file system the distribution resides on (hence adding the dist name to the .tar.gz filename so if you have 2 different modules at v0.0.1 you can still have both files saved in your author directory) 14:17
as far as .tar.gz vs .zip - well i guess you have to pick and choose. windows has native support for unzip, but not for .tar.gz. linux has native support for .tar.gz, but not usually for unzip. linux can more easily install unzip than windows can install an untar utility. but if the windows system has perl5 in their PATH they also have Archive::Tar, which zef will use. so .zip really is preferential 14:21
for *rakudo star* users on windows, since that can (I think) be installed without perl5
(fwiw windows can natively handle .gz too, just not .tar)
tbrowder ugexe: thanks. any suggestions for how to keep part of a repo separated without .gitignore? Will MANIFEST help that? 14:36
ugexe well if you aren't using github to generate your .tar.gz you would use whatever tool you are using understands
App::Mi6 i believe looks at .gitignore OR MANIFEST to generate a .tar.gz 14:37
however a MANIFEST shouldn't be needed - a META6.json loaded into a Distribution will provide $dist.meta<files>, which combined with $dist.meta<provides>.values gives you all the *usual* files you would expect 14:39
App::Mi6 could use that
tbrowder hm, independent gen of the archive sounds good if one can ti that in to github some way. what about making the META6.json allowing multiple source-url entries so we can use both zip and tar.gzip archives? 14:40
that would cure Zoffix's problem. 14:41
ugexe its something i would probably implement sooner than later 14:42
tbrowder s/ti that in to/tie that in to/
ugexe but other ecosystem tooling would have to understand it
tbrowder roger
ugexe so maybe it would have to be a new field, source-url-mirrors or something
tbrowder going to p6 conf in us-dc? 14:43
uh, TPC (AKA: YAPC::NA::2017)
ugexe heh, no. my sponser can't sponser me now because of policy changes + i'm a contractor 14:44
tbrowder are you a member of a PM grp? 14:45
ugexe no
tbrowder thanks, bye 14:47
14:47 tbrowder left
nine ugexe: the META6.json does not reference the test files 15:29
ugexe ah, well it could, but they'd be installed 15:47
(like bin/)
16:18 mst joined 16:54 domidumont joined 17:20 domidumont1 joined 17:25 domidumont joined 17:33 stmuk joined 20:09 stmuk_ joined, dwarring joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!