Open netkan-bot opened 9 years ago
netkan-bot
commented
9 years ago 
From @AlexanderDzhoganov on December 19, 2014 20:21
Hey, while this feature is very useful, it is already provided by our API. You can query http://api.ksp-ckan.org/Identifier/Version (or just use "latest" for the latest version) to fetch the respective metadata file.
netkan-bot
commented
9 years ago
From @hakan42 on December 19, 2014 21:14
@mutability, you have to keep in mind that the ckans from the api have modified download URLs... Just remember to rename them back if you use them as a basis for your own ones :)
netkan-bot
commented
9 years ago
From @mutability on December 19, 2014 22:22
mm - was really thinking of a purely local operation here. The registry files are hard to work with by hand.
(I find myself having to dig around in the registry occasionally to work out why ckan is doing what it's doing - I guess more generally a set of tools for working with the local state would be handy)
From @mutability on December 19, 2014 18:33
It'd be handy to be able to export the registry's info for a given mod-version as a ckan file. (At least, I don't see a way to do that at the moment)
Currently if you want to grab a ckan file that's part of the master metadata as e.g. the basis for an updated version, you have to go and track down the right ckan file from github, which is a bit fiddly when ckan should already have that info on hand locally.
Copied from original issue: KSP-CKAN/CKAN#645