Package Version

[dbent]

Is there a plan to incorporate a package version, i.e. a version number which indicates the revision of the package itself, not the upstream mod?

For example, a mod may release version 1.7 which produces the first package 1.7-1, however the packager forgot to specify the license so they repackage as 1.7-2, but then they realized they forgot to specify a dependency so they repackage as 1.7-3, then when the mod releases version 1.8, the packager releases package 1.8-1.

[pjf]

Presently we don't. Right now the behaviour of a ckan update is to forget everything about what's available, and then reload it all from any repos that are configured. Consequently, updating the meta-data in the repo will update what's available for all clients the next time they sync.

For installed mods, we record the metadata that we used at the time of the install, so we could detect that we're seeing different metadata from upstream, even if we don't have explicit package versioning to enumerate it.

It would be easy enough to add, although I fear if it were mandatory humans may forget to update it. ;)

[pjf]

Closing this for now. But if you think it's something we really should have, please feel free to re-open.