{"action":"created","issue":{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/102","labels_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/102/comments","events_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/102/events","html_url":"https://github.com/KSP-CKAN/CKAN-support/issues/102","id":60809665,"number":102,"title":"\"version\" field does nothing in metapackages","user":{"login":"Dazpoet","id":10254092,"avatar_url":"https://avatars.githubusercontent.com/u/10254092?v=3","gravatar_id":"","url":"https://api.github.com/users/Dazpoet","html_url":"https://github.com/Dazpoet","followers_url":"https://api.github.com/users/Dazpoet/followers","following_url":"https://api.github.com/users/Dazpoet/following{/other_user}","gists_url":"https://api.github.com/users/Dazpoet/gists{/gist_id}","starred_url":"https://api.github.com/users/Dazpoet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dazpoet/subscriptions","organizations_url":"https://api.github.com/users/Dazpoet/orgs","repos_url":"https://api.github.com/users/Dazpoet/repos","events_url":"https://api.github.com/users/Dazpoet/events{/privacy}","received_events_url":"https://api.github.com/users/Dazpoet/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/labels/%E2%98%85%E2%98%85%E2%98%85","name":"★★★","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-12T12:12:35Z","updated_at":"2015-04-14T17:27:52Z","closed_at":null,"body":"After playing around a bit with metapackages I noticed that the version field in them don't seem to have a function.\r\n\r\nCreating a simple metapackage like\r\n\r\n    {\r\n    \"spec_version\": \"v1.6\",\r\n    \"identifier\": \"YourMetapackageName\",\r\n    \"version\": \"1\",\r\n    \"license\": \"unknown\",\r\n    \"name\": \"User friendly name of your metapackage\",\r\n    \"abstract\": \"A short description of the metapackage\",\r\n    \"kind\": \"metapackage\",\r\n    \"depends\": [\r\n        {\r\n            \"name\": \"ModuleManager\",\r\n            \"version\": \"2.5.9\"\r\n        }\r\n\t]\r\n    }\r\n\r\nWill install the same version (2.5.10 as of this post) as this one\r\n\r\n    {\r\n    \"spec_version\": \"v1.6\",\r\n    \"identifier\": \"YourMetapackageName\",\r\n    \"version\": \"1\",\r\n    \"license\": \"unknown\",\r\n    \"name\": \"User friendly name of your metapackage\",\r\n    \"abstract\": \"A short description of the metapackage\",\r\n    \"kind\": \"metapackage\",\r\n    \"depends\": [\r\n        {\r\n            \"name\": \"ModuleManager\",\r\n        }\r\n\t]\r\n    }\r\n\r\nNot sure if this is by design or not but it's confusing to the end user (me) at least. I assume there might be times when you'd want a user to specifically install a certain version of a mod inside a metapackage and the current system makes it look like that would be possible but it isn't.\r\n\r\nIt should be noted that the installed-default.ckan file has the version fields so giving it a purpose would make that file a snapshot rather than the, perhaps, intended redistributable modlist it is now.\r\n\r\nI propose that if the version field is made to distinctly install specific versions through the use of metapackages that the installed-default.ckan have those fields removed as to make it easier for end users to just grab that file and send to their friends."},"comment":{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/comments/92989261","html_url":"https://github.com/KSP-CKAN/CKAN-support/issues/102#issuecomment-92989261","issue_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/102","id":92989261,"user":{"login":"JapaMala","id":288477,"avatar_url":"https://avatars.githubusercontent.com/u/288477?v=3","gravatar_id":"","url":"https://api.github.com/users/JapaMala","html_url":"https://github.com/JapaMala","followers_url":"https://api.github.com/users/JapaMala/followers","following_url":"https://api.github.com/users/JapaMala/following{/other_user}","gists_url":"https://api.github.com/users/JapaMala/gists{/gist_id}","starred_url":"https://api.github.com/users/JapaMala/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JapaMala/subscriptions","organizations_url":"https://api.github.com/users/JapaMala/orgs","repos_url":"https://api.github.com/users/JapaMala/repos","events_url":"https://api.github.com/users/JapaMala/events{/privacy}","received_events_url":"https://api.github.com/users/JapaMala/received_events","type":"User","site_admin":false},"created_at":"2015-04-14T17:27:52Z","updated_at":"2015-04-14T17:27:52Z","body":"I can confirm this issue, and add that it has caused a lot of confusion for a multiplayer server I'm on.\r\nThe CKAN file specifies a specific RealFuels config, which needs to be selected to not cause problems, but CKAN does not respect that, and asks the user to chose a config, giving no indication as to which is the right one."}}