[Sugar-devel] Bug No. #1442
garycmartin at googlemail.com
Mon Sep 20 21:17:54 EDT 2010
On 20 Sep 2010, at 21:54, Shanjit Singh Jajmann <shanjit at dev.seeta.in> wrote:
> I am actually facing problem with this particular bug( http://bugs.sugarlabs.org/ticket/1442 ), it would be helpful if a few pointers be provided. Also if someone could elaborate on how to check between sugar / activity Compatibility it would be helpful.
This seems a rather hopeful bug to really fix, I'm not clear there is an actual solution. Version support/awareness is currently covered/attempted by a mix of distro/deployment testing and the flags set when an activity maintainer uploads a new activity release to http://activities.sugarlabs.org. I understand the ASLO flagging may not be happening very well after an irc chat with David (dfarning) and have offered to at least try to sweep through 0.82 and flag wrongly categorised activities on ASLO.
I try to make the activities I look out for work on _all_ official Sugar releases, though this might have to break at some point given the likely code churn for future 0.92. I do test all my releases on 0.82, 0.84, and a recent Sugar build when available (0.88 usually, 0.90 pre releases are still pretty unstable to do much sane activity release work on other than obvious reported API breaks).
I understand it could be possible to introduce a minimal version support value by the developer in the activity.info file, but many activity breaks to my eye are new Sugar/distro releases that break some previously supported feature or dependancy. As an activity developer there is no obvious way to pre guess what features some distro or core Sugar developers may decide to drop in the future.
Sorry if that is not much help, there may well be some generic solution, but I don't see it just now — you have a tough bug!
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel