|
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 October 2017. |
|||
|
01:38
llfourn joined
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 | ||
| nine | ugexe: CompUnit::PrecompilationDependency::File serializes and deserializes CompUnit::DependencySpecification objects. | 05:40 | |
| ugexe: but "provides" is not about DependencySpecifications. It's about Longnames of modules. DependencySpecifications are for fuzzy matching of Longnames. Longnames are much simpler. | 05:41 | ||
|
07:02
domidumont joined
07:08
domidumont joined
08:14
domidumont joined
09:11
domidumont joined
10:33
llfourn joined
|
|||
| ugexe | Dependency specs can be long names, and provides does not allow a means of giving a long name | 13:34 | |
| I guess I don’t see why there should be a difference between how provides and depends each parse the names they contain | 13:40 | ||
| the items in provides are essentially the same as depends, with the difference being that `provides` includes the `:file<...>` portion of the long name (as a value to a key instead of directly ala Foo::Bar:file<...> but still) | 14:26 | ||
| which are also then used for fuzzy matching the same way as other depends | 14:29 | ||
| although I call this concept 'depspec' because i need to use it for non-cu dependencies (native) as well | 14:33 | ||
| gist.github.com/ugexe/4334edeb5402...ion-t-L264 shows an example of using provides in this way (with the meta data on lines 222 and 223) | 15:00 | ||
|
15:01
b2gills joined
16:04
domidumont joined
|
|||