On Wed, Jun 5, 2013 at 12:57 PM, James Tait <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 05/06/13 16:36, Martin Albisetti wrote: >> On Tue, Jun 4, 2013 at 9:40 PM, James Tait >> <[email protected]> wrote: >>> click_version: string (searchable, retrievable) # '0.1' >>> click_framework: string (searchable, retrievable) # >>> 'ubuntu-sdk-13.10' click_updown_url: url (retrievable) >>> countries_to_distribute: string (searchable, multi-value) >> >> >> So, I realised that we may want to also have "SDK version", which >> is really what the client can use to figure out what's installable >> or not. > > Separate from click_framework? I probably don't really know enough > about the specifics of the client, but I'd imagine they'd be aware of > what frameworks they support.
I think it's different. Think. Maybe Colin or Stuart can comment on it. I would guess that the click package framework itself would have different versioning than the SDK. I have been conflating them as the same, but maybe they're not. > This does raise a couple of interesting questions though, which I > forgot in my previous mail - will Click packages target a single SDK > and version, or will they be able to support multiple versions of > multiple SDKs? What about the clients? > > If packages can target multiple (SDK, version) combinations, we should > make click_framework multiValued. If clients can support multiple > frameworks, they can issue a query along the lines of > "q=click_framework(ubuntu-sdk-13.10 OR ubuntu-sdk-14.04)". Great question for Colin :) -- Martin -- Mailing list: https://launchpad.net/~ubuntu-appstore-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-appstore-developers More help : https://help.launchpad.net/ListHelp
