-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
KSP-AVC / CKAN future integration #387
Comments
We already partially use AVC files for indexing new releases. Or are you after AVC checking ckan metainfo for new releases? Because we'd be totally down with that. We might need to see if we can port the core to mono 3.5 (#330) to make it accessible via KSP compiled mods. We could potentially implement a Do we know if the AVC / MiniAVC folks are on github? |
That's affirmative, sir. https://github.com/CYBUTEK/KSPAddonVersionChecker, I'll create a similar ticket over there to initiate the conversation. |
References CYBUTEK/KSPAddonVersionChecker#6 |
Asking for clarification here? Do we want:
|
AVC to ask to launch CKAN to update when a mod update is available. Example gameplay:
|
In addition to Felger's last comment, what about the following (which would need to initiate on the AVC side):
AVC knows within minutes that there's an update, but CKAN can take a while, particularly if the mod author hasn't explicitly added support for CKAN. This way the AVC support becomes CKAN support. |
Alternate title: MAKE LIFE EASIER FOR FELGER RIGHT NOW PRIORITY ONE!!!!8!!!
As requested, I have created a ticket.
For the serious request, it'd be nice if there were some communication between KSP-AVC and CKAN to facilitate easy notification of mod updates.
The text was updated successfully, but these errors were encountered: