Discussion in FreeCAD-addons about using metadata.txt the way QGIS does
https://github.com/FreeCAD/FreeCAD-addons/issues/29#issuecomment-303949382
Is this something akin to the idea of Manifest.in ?
bump
I guess this comment is somehow related. https://forum.freecadweb.org/viewtopic.php?f=8&t=40749&start=20#p354989
Btw.: The Manifest.in is a list of additional files which should be packaged.
Hello, first of all, sorry to intrude in this discussion. I made the comment quoted above and I'm not sure it is related.
I maybe mistaken, but @luzpaz is asking for a way to describe dependencies of an addon, and I think the mechanism is already provided by setuptools for this kind of 'new style pip installable addon', if these dependencies are available for download. (see https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-dependencies)
As @looooo said, the classical use for Manifest.in is to include in the distribution additional files not readily identified as 'code' files, like resources or supplementary documentation.
This is being superceded by @chennes's work on the Addon Manager Package Metadata: https://wiki.freecad.org/Package_Metadata