Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fill more fields on $vref #1765

Closed
janbrohl opened this issue Jun 1, 2016 · 2 comments
Closed

Fill more fields on $vref #1765

janbrohl opened this issue Jun 1, 2016 · 2 comments
Labels
Enhancement New features or functionality Netkan Issues affecting the netkan data Spec Issues affecting the spec

Comments

@janbrohl
Copy link
Contributor

janbrohl commented Jun 1, 2016

https://github.com/KSP-CKAN/CKAN/blob/master/Spec.md#vref states that only KSP version info is extracted although several other fields map well to ckan.

  • NAME: name
  • GITHUB: resources.repository (or even $kref for github)
  • VERSION: version
  • DOWNLOAD: resources.homepage

CHANGE_LOG and CHANGE_LOG_URL do not yet map to a ckan-fields but having having or linking to a changelog in ckan (resources.changelog?) seems like a good thing to me. Propably there is a reason why there is no such field but what is it?

@politas
Copy link
Member

politas commented Jun 1, 2016

We really can't use the $vref to fill in the $kref, since we need the $kref to find the download where we can see the $vref. I don't think we have the ability to put a URL in a $vref, yet.

As a basic note, mod authors don't always get the .version files exactly right, or keep them updated consistently.

@janbrohl
Copy link
Contributor Author

janbrohl commented Jun 1, 2016

Theoretically $kref could be filled that way if the download-field is provided - but that would make $kref much less useful.

@ayan4m1 ayan4m1 added Enhancement New features or functionality Netkan Issues affecting the netkan data metadata Spec Issues affecting the spec labels Aug 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New features or functionality Netkan Issues affecting the netkan data Spec Issues affecting the spec
Projects
None yet
Development

No branches or pull requests

3 participants