Skip to content
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

Open
glensc opened this issue Jan 21, 2019 · 7 comments
Open

new fields to {plugin,template}.info.txt #2678

glensc opened this issue Jan 21, 2019 · 7 comments

Comments

@glensc
Copy link
Contributor

glensc commented Jan 21, 2019

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, example 7.1
  • dokuwiki: minimum php version supported, example 2018-04-22

altho for php and dokuwiki 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.

@Klap-in
Copy link
Collaborator

Klap-in commented Jan 21, 2019

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.

@splitbrain
Copy link
Collaborator

In addition, the license field is pretty much useless as it would always say GPL2

@Klap-in
Copy link
Collaborator

Klap-in commented Jan 21, 2019

about the prosemirror plugin: I guess the lowest will be the PHP version current supported by DokuWiki itself.

@lpaulsen93
Copy link
Collaborator

What about a field like dependencies to list other plugins which need to be installed to make a plugin work.

@glensc
Copy link
Contributor Author

glensc commented Jan 21, 2019

I mean if plugin generator adds composer.json and dokuwiki itself supports reading it, then the both files can be supported and the .info.txt format retired eventually.

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 package.json from plugin dir.

@glensc
Copy link
Contributor Author

glensc commented Jan 21, 2019

i have filled php version in one of my plugins, and dependencies for bundling:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants