On Fri, 2014-10-24 at 18:10 +0200, Nekhelesh Ramananthan wrote:
> I know and agree, but that is a limitation which will prevent me from > improving the clock app further. Let me provide an example to explain > this better. With 15.04 development cycle open, the SDK developers are > planning to add new listitem components which are supposed to bring > about performance improvements and also customization options to the > app developer. However when this lands, the frameworks version will be > bumped to ubuntu-sdk-15.04-qml-dev. Clock app at the moment uses > ubuntu-sdk-14.10. Now if I bump clock app's framework version, then > any bug fixes that I push to clock app trunk cannot be backported to > rtm devices since they ship with ubuntu-sdk-14.10. The new listitems > are absolutely critical since they will allow me to remove a lot of > custom code that I have to maintain and rely on official well tested > upstream sdk components. I think the only way to fix that is to somehow enable conditional runtime dependence on the frameworks. If your target is RTM, you shouldn't be developing against a newer version of Ubuntu than RTM is. You can only use frameworks available in RTM for core apps, I think. You will have to wait until RTM is done and we move to a Vivid based image for future OTA updates for customers, before being able to use newer frameworks. You can create a branch to develop features that depend on new API in, and then merge it back to trunk when those features are usable in a supported image. But I don't see any way for supporting multiple different framework versions in an app, on a system that is designed to be a single rolling release. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
