Implementing a plugin updater + dependency management + semantic versioning
#6
Here is the library SphinxC0re mentioned: https://github.com/zmarko/semver
Though as I said I don't think we can use it because it uses C++14 while were using C++11.

So you'd save the name of the plugin, the configuration file, (database possibly?) and a link where it can be downloaded? This would also mean that developers needs to mention where the configuration file (and possible the database) is. I guess that's possible, but I still don't think we should hardcode an updater inside the server. It makes more sense to me to let another plugin handle it.

Also, I don't think this change would, but I'll mention it: Would this change break our current plugins?

Finally I'd like to point out that I'm pretty frustrated that we're getting this discussion after I've finished my updater functionality in WorldEdit. I mean, come on the PR was there for 9 days, couldn't we talk about it back then?
Reply
Thanks given by:


Messages In This Thread
RE: Implementing a plugin updater + dependency management + semantic versioning - by NiLSPACE - 01-29-2016, 01:38 AM



Users browsing this thread: 7 Guest(s)