Add an optional version field to the Sirdi manifest format.
This can be expanded upon to hook into dependency resolution in the future, but my motivation thus far is a bit more basic: support the fields I already put in ipkg files to begin with.
As a package maintainer, I want to support Sirdi but also hold onto my existing ipkg file so I can support users that prefer what Sirdi considers a "legacy" install. To do this, it would be ideal if running a sirdi build did not destroy information in my ipkg file.
All the fields I want to specify can be specified in passthru except for version, which is not a string value. Since I think that using versioning could become a robust strategy for Sirdi dependency resolution, adding the version field like this feels like a win-win for now.
Add an optional version field to the Sirdi manifest format.
This can be expanded upon to hook into dependency resolution in the future, but my motivation thus far is a bit more basic: support the fields I already put in
ipkgfiles to begin with.As a package maintainer, I want to support Sirdi but also hold onto my existing
ipkgfile so I can support users that prefer what Sirdi considers a "legacy" install. To do this, it would be ideal if running a sirdi build did not destroy information in myipkgfile.All the fields I want to specify can be specified in
passthruexcept for version, which is not a string value. Since I think that using versioning could become a robust strategy for Sirdi dependency resolution, adding the version field like this feels like a win-win for now.