Conversation
Do NOT merge this PR until AFTER branch "fixes_issue_2697_ClickThroughBlocker" finds its way all the way into a public release in a ZIP file. The reason is complex, but it has to do with how CKAN's bot crawls and reads the kOS.netkan file. As soon as this edit finds its way into the master branch, CKAN's bot will see it within a half hour. If it sees this edit *before* we make a release from that master branch, it will end up associating these edits with the previous kOS release, and falsely adding this new dependency to it. In general all edits to kOS.netkan MUST wait until after there's been a release made for those edits.
|
NOTE - This is not merged because I had to back-out the merge of #2729 and the clickthroughblocker dependency isn't there yet. Unless the issue I had with it is addressed, I can't make kOS depend on it. |
|
Hi @Dunbaratu, I just stumbled on this while investigating something else and read your https://github.com/KSP-CKAN/CKAN/wiki/Adding-a-mod-to-the-CKAN#internal-ckan-files
A file with a I have been using this approach for my own mods for a while now and I like it pretty well. Astrogator now has a very minimal .netkan file and a more verbose .ckan file: |
2 participants
This is associated with PR #2729. When PR #2729 is merged, then wait until that merge makes its way into a public release ZIP, and immedaitely after that ZIP is made public, THEN merge this PR into develop and into master.
To see why, see the documentation files that this PR itself edits, which describe this new policy I'll try to adhere to from now on.