{"action":"created","issue":{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/39","labels_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/39/comments","events_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/39/events","html_url":"https://github.com/KSP-CKAN/CKAN-support/issues/39","id":53121430,"number":39,"title":"Proposal: Synchronize CKAN mod lists between installations","user":{"login":"Eddlm","id":7364336,"avatar_url":"https://avatars.githubusercontent.com/u/7364336?v=3","gravatar_id":"","url":"https://api.github.com/users/Eddlm","html_url":"https://github.com/Eddlm","followers_url":"https://api.github.com/users/Eddlm/followers","following_url":"https://api.github.com/users/Eddlm/following{/other_user}","gists_url":"https://api.github.com/users/Eddlm/gists{/gist_id}","starred_url":"https://api.github.com/users/Eddlm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Eddlm/subscriptions","organizations_url":"https://api.github.com/users/Eddlm/orgs","repos_url":"https://api.github.com/users/Eddlm/repos","events_url":"https://api.github.com/users/Eddlm/events{/privacy}","received_events_url":"https://api.github.com/users/Eddlm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-12-30T15:09:09Z","updated_at":"2015-01-01T11:40:10Z","closed_at":null,"body":"From http://forum.kerbalspaceprogram.com/threads/100067-The-Comprehensive-Kerbal-Archive-Network-%28CKAN%29-Package-Manager-v1-5-0-24-Dec-2014?p=1638484&viewfull=1#post1638484\r\n\r\nCKAN could have a way to export a modlist to a file so other instances of CKAN could import that file and install the exact same list of mods on another KSP installation. It could help to synchronize modlists between different KSP installations, allowing them to have the same mods installed.\r\n\r\nSituations in wich this could be helpful/useful:\r\n   1. People who need to reinstall KSP. Having a list of mods for CKAN to import, download and install would ease the process of leaving the new KSP like the old one was.\r\n   2. People (like me) who wish to keep two KSP installations synchroniced (mod-wise). For example, a main PC installation and a laptop installation.\r\n   3. Youtubers wich have the \"What mods I used\" thing could replace enormous modlists with a simple link to a CKAN mod synchronization file.\r\n   4. It could allow people to make \"modpacks\" in form of exported modlists (A \"realism overhaul\" modlist, a \"Exploration\" modlist, etc), wich they could post somewhere for others to download and let CKAN handle it for them.\r\n\r\n   That way of handling modpacks could help avoid the \"NO REDISTRIBUTION\" problem wich some mods have, preventing people from adding them to modpacks. As CKAN, when downloading mods, uses the original links the author provided, there's no \"no redistribution\" rule infringement.\r\n In this situation CKAN could also become a \"modpack installer\", basically.\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/comments/68484888","html_url":"https://github.com/KSP-CKAN/CKAN-support/issues/39#issuecomment-68484888","issue_url":"https://api.github.com/repos/KSP-CKAN/CKAN-support/issues/39","id":68484888,"user":{"login":"Eddlm","id":7364336,"avatar_url":"https://avatars.githubusercontent.com/u/7364336?v=3","gravatar_id":"","url":"https://api.github.com/users/Eddlm","html_url":"https://github.com/Eddlm","followers_url":"https://api.github.com/users/Eddlm/followers","following_url":"https://api.github.com/users/Eddlm/following{/other_user}","gists_url":"https://api.github.com/users/Eddlm/gists{/gist_id}","starred_url":"https://api.github.com/users/Eddlm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Eddlm/subscriptions","organizations_url":"https://api.github.com/users/Eddlm/orgs","repos_url":"https://api.github.com/users/Eddlm/repos","events_url":"https://api.github.com/users/Eddlm/events{/privacy}","received_events_url":"https://api.github.com/users/Eddlm/received_events","type":"User","site_admin":false},"created_at":"2015-01-01T11:40:10Z","updated_at":"2015-01-01T11:40:10Z","body":"MMh, I don't really see the difficulty. In fact, as CKAN has all the mods separated in different files, something along the lines of\r\n$ckan list > list.txt\r\n$for /f %%mod in list.txt do ckan install %%mod\r\ncould work.\r\nIt wont as ckan list puts more info than simply the installed mod identifiers...\r\n\r\nI don't know how to code for CKAN, but the idea should be simple. A new command wich exports the installed mods to a plain text mods.ckan file, and a command wich loads identifiers from mods.ckan and installs them. We would be using already existing CKAN features (the default ckan mod installing procedure).\r\n\r\nAt least, this would work for the commandline mode. The GUI mode would do the same, but adding a window to select wich mods.ckan file you want to load."}}