https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24631 --- Comment #13 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to Martin Renvoize from comment #11)
I'm happy with whatever name.. META.yml probably came out of a discussion Kyle and I had about using cpan's packaging system for inspiration.. meta.yml, plugin.yml. koha.yml.. I'm not too worried about a name so long as we document it.
As for requiring module load prior to reading the yml.. hmm, does feel like we should be able to get that path info from the plugin base code koha side somehow.. A chunk of this is actually about how we then expose the new meta file next to releases on github (and eventually gitlab) so we can grab that data via api's and display/use it prior to install entirely.
I'm doing my best to keep Koha backwards compatible with plugins that have no META.yml file. I definitely think we should consider ignoring plugin releases without a META.yml file for searching purposes. -- You are receiving this mail because: You are watching all bug changes.