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 25 January 2016.
02:56 Kassandry joined 04:32 Kassandry joined 07:22 domidumont joined 07:23 domidumont joined 07:28 domidumont joined 08:03 FROGGS joined 09:24 leont joined 15:07 lizmat joined 15:11 lizmat joined 15:57 cognominal joined
jdv79 do we have anything like rpm's virtual pkgs? 16:25
sjn jdv79: there's a "provides" field, but strictly speaking we don't have any virtual packages (in RPM's sense) 16:29
Although I _am_ a fan of extending the notion of "dependency" to include services and system resources, and that might perhaps cover some of the use cases RPM virtual packages handle now 16:31
jdv79 wonder if that has to be proxied through concrete namespaces (like Alien) or if there could be another way. 16:36
i have no idea. just thinking out loud. 16:37
or, how could i say i provide or require some interface or api? and then how does an installer satisfy that? 16:40
tony-o_ jdv79: could roles fill that gap? 16:43
or help, at least 16:47
essentially a module that does virtual HTTP::Server and is most used or <whatever criteria> can be offered with it 16:48
HTTP::Server is a role
ugexe a module name only (without its auth/ver/api) is already a virtual package: `use Foo::Bar;` will use whatever foo bar you installed. similarly s22 defines augments, emulates, supercedes, and superceded_by
tony-o_ i don't think that satisfies the guaranteed interface/api 16:55
17:31 domidumont joined 17:39 FROGGS joined 17:57 leont joined 19:21 Kassandry joined 19:37 leont joined 20:44 lizmat joined 22:24 FROGGS joined