|
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 24 March 2016. |
|||
|
07:40
domidumont joined
07:45
domidumont joined
10:08
FROGGS joined
10:11
pnu joined
10:30
pnu joined
10:51
pnu joined
11:14
pnu joined
11:30
sivoais joined
16:28
Kassandry joined
|
|||
| ugexe | last thing i need to hammer out is how to treat special directories vs resources. For instance: resource might contain a build-time file (.platform-library-name) or a files that already exist, but all of them go into `files`. This is different from `bin` where all the files were (currently) expected to exist as part of the actual archive | 17:11 | |
| one solution may be to use `files` to contain all files (currently doesnt list provides), or to only list files that aren't otherwise implied in the meta6 itself (resources is already implied in `resources`, but `bin/` has no such section) | 17:13 | ||
| otherwise we will hit trouble when/if we start hashing all files of a distribution | 17:27 | ||
| because you can extend the meta6.json sure, but the contents get changed so requires reconstructing that as well | 17:29 | ||
| jdv79: do you remember anything missing from the meta6 that would be helpful for metacpan? | 17:38 | ||
|
17:46
cognominal joined
18:09
domidumont joined
|
|||
| ugexe | maybe makes more sense to create file-id as `!file-id($dist-id, $name)`. then it follows a pattern that allows adding an additional prefix to be more specific (self!repo-prefix, $dist-id, $name) | 20:47 | |
| instead of !file-id($name, $dist-id) | 20:48 | ||
| hell maybe !file-id could be in a role for CURI as well as Distribution, so Distribution can essentially know the hashing algorithm used for whatever CUR its from | 21:05 | ||