hakan

You know there is always that one more mission you wished you could have gotten to

Nope, but it gives you a hint that updates are available. The choice is in your hands.

Actually, the main thing holding up TWP (and, by extension, KAC) is the fact that the zip entries start with <modname>-<modversion>/GameData/TriggerTech instead of GameData/TriggerTech like nearly all other mods out there. We either have to implement an extension in ckan (the infamous "find" keyword) or TriggerAu could help us a little bit by changing his packaging structure. Anyway, as soon as one or both of those things are tackled, the addons should appear, as if by magic, on CKAN

Really? I have to test this, but if it works, it would make some of my work tremendously easier True... But then again, one of the first ideas was that there should be no additional burden on the mod author, which also lead to the success of CKAN. Do you mind to open up an issue on github for your suggestion so it does not get buried in the forum?

Aaaaaaaaaaah, yes, big assumption on my side too that the version checker code would consider an empty "ksp_version" as infinitely big... But don't quote me on it Nope, we try to keep version indefinitely. If something really really needs to be deleted, you need to set up a pull request with a "git rm" in it, but the consensus is to keep the ckans, assuming we can download the zip files, too. If the zip itself is gone, there is not much we can do about it anymore. Besides mirrors of course, but that's another can of worms that you never did hear me opening

Actually, pretty easily. AGX-1.24c.ckan has ... "version" : "1.24c", "ksp_version" : "0.25" ... in it, and AGX-1.25d.ckan has ... "version" : "1.25d", "ksp_version" : "0.90" ... If you write a netkan for AGX and have your releases on Kerbalstuff, and mark your releases with the proper version numbers, there is a pretty good chance that the netkan-bot will automatically create the above ckan files for you. What I am not sure is, though, whether it would go and create ckans for all the releases, thereby giving you both, or considers only the latest release. Need to experiment here.

Well, if this is the opinion of Starstrider as well... The thing is, KS gives us much richer metadata without needing human intervention...

We have the badge at github issue #526 (which reminds me, I wanted to export that and add it as an icon to the main site), and the icons at https://github.com/KSP-CKAN/CKAN/tree/master/CKAN/assets By the way, is the KerbalX site itself on github? I had a few ideas here and there and would love to send pull requests if I would ever get around to implement something...

Would you mind terribly to upload this release to kerbalstuff and mark it there as "0.90"? CKAN is set up to follow KS for RemoteTech

http://api.ksp-ckan.org/ and then you can go through the JSON file you get from there. Every mod and version has its own subpage as well, like http://api.ksp-ckan.org/MechJeb2/2.4.1 Actually, I think a best effort guess might already be enough. you might want to create a lookup table with folder name and mod name columns in it, and put any exceptions in there if the first guess proves wrong.

It is only a basic json file in your plugin zip. You just have to generate it at your build time so it reflects exactly the version you are building... On the other hand, if you could implement the AVC file, it would help on the CKAN side as well as we could extract additional metadata from it, leading to even less human work Exactly what CKAN was designed to do, my dear sir!

Much better now, I will check your other plugins later tonight... (christmas tree work waiting) One thing, though: Do you think that you could drop the top level from your zip files? So they are only "GameData/<whatever>" instead of "<whatever-x.y.z>/GameDate/<whatever>"? We have an issue waiting in the CKAN project to implement a solution for this, but in the meantime, you could help tremendously if your zip files would look like the zips of nearly all other mods

nlight said something on IRC about travis (our build system) acting up and doing strange things...

Adding that to CKAN may be possible but it would definitely be easier if it would not be a huge 230 MB blob... Let me download it and see whether it might be split in config files and dependencies to other mods...

That's a reeeeally coll old-timey video

The handrails are working for me on 0.90, so it would be wonderful if Krasimir would mark it as "0.90" over on kerbalstuff. Then, through the magic of our robots, all CKAN users would be able to one-click install the rails

I hate my life... o.k., let me test a bit, we still might get to the bottom of this... Actually, would you mind terribly to go to https://github.com/KSP-CKAN/CKAN/issues and open up a github issue about this? I'm not sure whether we already have one...

did you run ckan upgrade before?

Yes, I believe nlight found something to this effect yesterday... Could you try to remove and re-install ScienceAlert via ckan? I believe then, you should be offered the 1.8.3

You seem to have set the string "KSP Version: 0.90" as version on kerbalstuff, which causes CKAN some serious trouble. ( https://kerbalstuff.com/api/mod/195 ) Could you please change this to "0.90" so our robots can pick up your release?

Do you think you could recognize whether a mod is already on CKAN and display an appropriate icon? Like kerbalstuff already does?

Automatic, the magic of netkan doing our work for us

Yes, a "ckan upgrade" would overwrite your dll. As for now, CKAN only keeps a list of file names, but not of the contents (or hashes) of each file inside the mod. But never fear, indexing sarbian's Jenkins server is just around the corner... I need to take vacation from work to finish all that CKAN stuff I have in mind

I am working on just that, http://munich.ksp-ckan.org/SCANsat-pre/mirror/ will hold the SCANsat... http://munich.ksp-ckan.org/MechJeb2-pre/mirror/ the MechJeb2 development builds... A proper announcement will be made when I have the client side done as well ( follow https://github.com/KSP-CKAN/CKAN/pull/563 over at github if you want early notification)

By now, you should see UniversalStorage 1.0.0 in your CKAN client.