[Sugar-devel] Changing bundle_id and version scheme for Etoys

[Walter Bender]

On Thu, Jul 22, 2010 at 12:49 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 22.07.2010, at 12:18, Lucian Branescu wrote:
>
>> I was thinking of changing
>> the bundle_id of Browse-webkit from 'org.laptop.WebActivity' to
>> 'org.sugarlabs.WebActivity', to allow both Browse to be installed and
>> working at the same time. However, this might confuse users yet again,
>> since they'd have their good old Browse along with a possibly broken
>> one.
>
> I have a similar problem. The bundle_id for Etoys is org.vpri.Etoys because the activity was initially developed at VPRI. Now that VPRI is not involved anymore we should change it to e.g. org.squeak.Etoys to reflect the new organization.
>
> Also, for some time I wanted to change the versioning scheme. I used to increment the version number and release a new activity bundle whenever something in the base system's etoys changed, even if there was no change to the activity itself (the bundle is just a thin wrapper). That doesn't really make sense. I was hoping Sugar's new "dotted-version" scheme would arrive in time for this, but has it?
>
> But what about existing Journal entries? They would still be tagged with the old bundle id, though the mime type would identify them as Etoys projects. If the old activity was uninstalled, would the new one automatically open those entries?''

I don't know of a solution to this problem except that mimetypes will
mitigate some of the problem. Updating is another problem... AFAIK,
the updater uses the bundle_id.

-walter

>
> - Bert -
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org