-
-
Notifications
You must be signed in to change notification settings - Fork 849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new fields to {plugin,template}.info.txt #2678
Comments
for example, I created new rpm package, but don't know the versions, so filled arbitary ones: |
It is for a lot of authors already a challenge to write in that file the right update date. So I guess the other properties are ignored more often. Or there should be something in place that helps and corrects/fills this kind of stuff for the authors. Does all these files have already a direct use for the authors? Otherwise I don't expect these are filled at all. |
In addition, the license field is pretty much useless as it would always say GPL2 |
about the prosemirror plugin: I guess the lowest will be the PHP version current supported by DokuWiki itself. |
What about a field like |
I mean if plugin generator adds and with composer, plugin authors don't really need to edit the text file, git tag is sufficient, yet this would require using composer ecosystem fully, not just |
i have filled php version in one of my plugins, and dependencies for bundling: |
For packaging and figuring out the license, PHP version, minimum supported DokuWiki version I think the following keys are in order:
license
a license keyword from https://spdx.org/licenses/php
: minimum php version supported, example7.1
dokuwiki
: minimum php version supported, example2018-04-22
altho for
php
anddokuwiki
keys, could use composer like syntax:^5.3 || ^7.0
or otoh, maybe not to invent something new, switch to use composer
composer.json
format? this would require publishing DokuWiki releases in packagist.org, which is not that bad idea at all.The text was updated successfully, but these errors were encountered: