[Bugs] #1053 UNSP: bundle gets installed each time it is started from Journal
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Mon Jul 13 16:37:14 EDT 2009
#1053: bundle gets installed each time it is started from Journal
------------------------------------------+---------------------------------
Reporter: sascha_silbe | Owner: tomeu
Type: defect | Status: new
Priority: Unspecified by Maintainer | Milestone: 0.86
Component: sugar | Version: Git as of bugdate
Severity: Minor | Resolution:
Keywords: r? | Distribution: Unspecified
Status_field: New |
------------------------------------------+---------------------------------
Comment(by garycmartin):
>Just for information (this patch doesn't change anything about it and
it's IMO out of scope for this bug): When resuming >existing instances it
will use the last installed version. Other options would be:
>a) the version the instance was created with
>b) the latest available version.
FWIW, as a developer I quite like the current behaviour. It allows me to
have different Activity bundle versions in Journal, install and test with
the specific version I want. Choice a) would be a bad IMO as when I
upgrade an Activity to the latest shiny version I want to access all those
lovely new Activity features if I open up existing work; choice a) also
assumes you have a all previous versions of an Activity bundle available
to install. Choice b) is OK, but prevents me from working with different
versions (say I'm hacking on my own version of Write, but still want to be
able to use the older official one.
Actually, having been exposed to the git hash scheme of things, I've fast
gone off version numbers :-) I'm not sure how I could use Sugar to safely
hack on a new version of any Activity, and not risk get clobbered by an
official release with that same sequential version number a little later.
--
Ticket URL: <http://dev.sugarlabs.org/ticket/1053#comment:1>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list