[ckan-dev] Revisions not in seperate Packages?

[Adrià Mercader]

Hi Michael,

On 7 December 2014 at 22:49, Michael Speth
<spethm at landcareresearch.co.nz> wrote:

> Why isn't there a separate file for the revision versions?
The only officially supported version at any one point is the latest
patch release (eg 2.2.1) for a particular minor version (eg 2.2), so
it makes sense to only have a file including the latest one. More
details on CKAN releases can be found here:

http://docs.ckan.org/en/latest/maintaining/upgrading/index.html#ckan-releases


> 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?
Perhaps checking if the md5 sum has changed? It would involve similar
work to check for the file name as you were suggesting.

http://packaging.ckan.org/md5sum

Adrià


>
>
> 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
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>