[ckan-dev] Revisions not in seperate Packages?

Michael Speth spethm at landcareresearch.co.nz
Sun Dec 7 22:49:45 UTC 2014


Currently, only the major and minor numbers are stored in the deb package<http://packaging.ckan.org/> file name.  I think this is problematic especially when attempting to automate<https://forge.puppetlabs.com/conzar/ckan> the upgrade process.

Questions Regarding revisions

  *   Why isn't there a separate file for the revision versions?
  *   If you are unable to produce a separate file (maybe political reasons???), how can the puppet ckan module identify that a new revision has been released?

Regards

--
Michael Speth
DevOps Computer Engineer
Landcare Research Consultant

________________________________

Please consider the environment before printing this email
Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20141208/fe279610/attachment-0002.html>


More information about the ckan-dev mailing list