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 22 September 2017.
tbrowder maybe something like “resources”: [ “man/man1/myinfo.1”] 01:24
01:56 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
03:03 llfourn joined 05:21 lizmat joined 06:52 domidumont joined 06:58 domidumont joined
tbrowder i believe installation of an ecosystem module needs to automaticall result in docs available to the user. is there any disagreement with that? 10:36
lizmat not from me :-) 10:37
11:30 leont joined
tbrowder lizmat: see my reddit post just completed 11:57
12:26 leont_ joined 12:27 leont joined 12:38 llfourn joined 12:59 leont joined
lizmat tbrowder: URL ? 14:42
tbrowder: nm, reddit, not HN :-) 14:43
www.reddit.com/r/perl6/comments/71..._6_versus/ # for the lazy ones 15:30
stmuk tbrowder: Its not a technical issue. What you describe would happen if people wrote pod for perl6. The problem is they don't. 17:35
they mostly just write a README.md
actually I mean embedded pod since I don't think S22 supports external .pod6 files 17:37
18:12 lizmat_ joined
ugexe it would be nice if github ever parses pod6 so we can have README.pod6 show up like README.pod/README.md on github 20:04
mst maybe figure out what hilighter they're using, contribute perl6 support? 20:20
stmuk github.com/github/markup/issues/907 20:33
tbrowder I just found out about p6doc as an installable module. IMHO, it needs to be part of any package for a new installation of rakudo. The user shouldn't have to install anything else to be able to read what Perl 6 pod is available. Also, p6doc needs to find ALL Perl 6 pod in a distribution. 23:34