[Github-comments] [geany/geany] [Plugin manager] Small improvement? (#2142)

[Colomban Wendling]

As @elextr said, there isn't really anything such as "geany-plugins" when it comes to Geany or the plugin manager -- geany-plugins is just an umbrella for a collection of individual plugins.

> I think it makes sense to see the package also as no one will ever take a plugin out of the package and install it stand-alone.

Take it out, no, but it's totally possible to install only some of the plugins, and they all are disabled automatically if their dependencies are missing at build time and they didn't get explicitly enabled -- meaning it's extremely easy to get a partial collection.
And as @elextr mentioned, when using downstream distributors, it's even more common to have each plugin separate, and possibly a meta-package merely installing them all.

> Looking at the plugin API I saw that the version is a string. So plugin developers could theoretically add the PACKAGE_STRING to the version. But that would meany each plugin of a package would need to do this manually to have a consistent look, so not very beautiful.

Yes, each plugin could set its version to include the "geany-plugins" version in it.  Or it could simply use the "geany-plugins" version as the plugin's version, which quite a few plugins do.  **If** there is enough of a rationale, I could imagine all plugins adopting this versioning scheme.

---

All this said, if it's really to make sure the expected build that is used, better look at the filename for the plugin library that is displayed in the tooltip when hovering.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2142#issuecomment-490261482
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20190507/e694f568/attachment.html>