Propagating changes from meta.yml to README, opam, etc. should be easier

[anton-trunov]

Meta-issue

I'd like to have a make target, something like make update_from_templates or some other short and nice name, so every time I update meta.yml I can easily propagate the changes using from mustache templates into destination files.
This means we would probably need to separate the coq-community templates into a git repo and include them as a submodule into the projects that use the templates. I'm happy to hear about any other alternative that solves the issue!

[palmskog]

I personally don't mind splitting out the mustache templates to a separate repo with dedicated documentation, etc. However, I'm not at all fond of the idea of using git submodules in any way or form, at least in the projects I maintain. There may be some third option that @Zimmi48 and I can figure out in the near future...

[anton-trunov]

I'm not at all fond of the idea of using git submodules in any way or form

That's precisely my feeling too :)

I'm looking forward to the solution you mentioned.

[Zimmi48]

With @palmskog, we are going to try out splitting the repo like you suggested during this week.

[Zimmi48]

I discovered another organization that is massively using automatic generation of support files from a meta yml file: https://github.com/conda-forge/coq-feedstock#about-conda-forge

[Zimmi48]

Another possible source of comparison / inspiration:
https://github.com/voxpupuli/modulesync (tool)
https://github.com/voxpupuli/modulesync_config (templates)