I'm not sure that creating a new tool from scratch because the existing tool isn't perfect is the best approach.
Yes, I think that this metadata thing was the original idea of this thread.Most of the problems of extension managers can be solved just with proper Metadata.
...
ref: Metadata thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=57448
I think that the metadata description is way too complicated, overengineered.chennes wrote: ↑Sun Jul 04, 2021 7:40 pm See also Pr 4787: https://github.com/FreeCAD/FreeCAD/pull/4787
…which includes a first cut at implementing the metadata format we discussed.
The metadata file must be a valid, well-formed XML 1.0 document. It must be called "package.xml"
Code: Select all
<version>1.0.0</version>
<maintainer email="email@freecadweb.org">No Maintainer</maintainer>
<url type="repository">https://github.com/FreeCAD/FreeCAD</url>
The original request was to be able to identify installed and available versions of addons. This is some sort of metadata, but please, make this simple. The AddonManager needs to know:
- the name of the extension (workbench, macro, preference pack ...)
- the URL and protocol to fetch it (doesn't have to be git)
- an icon (optional)
- a description (optional)
- the currently installed version (optional)
The package needs to provide :
- the current version
- the license