https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24631
--- Comment #9 from David Cook <[email protected]> --- (In reply to Julian Maurice from comment #8) > (In reply to Kyle M Hall from comment #6) > > (In reply to Julian Maurice from comment #5) > > > Hi Kyle, > > > > > > Can you comment on why you chose to name the file META.yml ? Is it related > > > to https://metacpan.org/pod/CPAN::Meta::Spec ? > > > > You are essentially correct. The file name is inspired by CPAN's > > META.yml/META.json file. > > Won't that be a problem if people want to publish their plugins on CPAN ? I was wary of using META.yml for a name due to its CPAN significance, but publishing plugins on CPAN seems problematic. It seems to me the plugins are their own packages and that the metadata file is part of that packaging scheme, so I don't really see the overlap. Like you could publish the module for a Koha plugin on CPAN, but you'd have to download it and package it into a KPZ and at that point you could provide the META.yml file. That said, maybe META.yml is just too close for comfort. Maybe KMETA.yml or KPMETA.yml? Just to make it a bit more distinctive? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
