Spec extension proposal: "supported_arch" and "supported_os"

[AlexanderDzhoganov]

I propose that we implement an extension called 'supported_arch'

"supported_arch" : {
            "description" : "Whether the mod supports 32-bit or 64-bit KSP or both",
            "enum" : [ "x86", "x64", "any" ]
}

and another one called 'supported_os'

"supported_os" : {
            "description" : "Which OS the mod supports",
            "enum" : [ "linux", "windows", "macosx", "any" ]
}

The reason for this proposal is that I feel like it would be nice to at least issue a warning if the user is installing a mod that won't work or will break his install. We can provide a way for the user to specify whether he's using 32 or 64- bit KSP in both clients.

[pjf]

Hooray! Anything which starts with an x_ field is guaranteed not to be used by the CKAN core (the spec forbids it), and consequently can and should be used for things like this.

So for this, #487, and #488, my response is JFDI if this is simply an extensions field. :)

Having said that, something like this does make sense for being in the core spec, although I 'd combine these into a single field, with values of linux, macosx, win32 and win64. The reason being that for a lot of mods, it's only win64 that has problems; having two fields means one can't exclude the problem build without excluding the stable 64-bit builds on other platforms.

[prometheanfire]

Since everything runs through mono on all three OS's I'd think all we'd need is x86 and x86_64. I haven't seen a mod author release a linux or osx specific version of their mod.

:+1: on this though :D

[legolegs]

Fly By Wire have separate releases for linux and windows. Don't know why exactly though.

[prometheanfire]

Ah, I do know that at least :P It's because linux has diferent input libraries, don't know why they can't be combined though.

[vosechu]

I would second splitting them up. It's not that much more typing, but if there's concern about that can we provide a sane default in the wiki and let people cut/paste?

[vosechu]

also, is there a convention for promoting a flag from x_ status to core? By which I mean, could we start with x_arch and just let it stew for a bit?

[netkan-bot]

Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automaically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it!

[prometheanfire]

feature request should still exist :P

[techman83]

I think it was closed by mistake :)