[Bugs] #1053 UNSP: bundle gets installed each time it is started from Journal

SugarLabs Bugs bugtracker-noreply at sugarlabs.org
Mon Jul 13 15:22:55 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                      |       Keywords:  r?               
Distribution:  Unspecified                |   Status_field:  New              
------------------------------------------+---------------------------------
 Each time a bundle (itself) gets started from Journal, it will be
 installed, even if the same version is already installed.
 From the IRC discussion:

 {{{
 20:43 < silbe> tomeu: is it on purpose that we install a bundle each time
 it is "started"
                from Journal, even if the same version is already
 installed?
 20:43 < tomeu> silbe: not at all
 20:45 < silbe> though as i think about it, maybe it's the lesser evil
 20:47 < silbe> the issue i'm thinking about is what happens if a
 user=activity developer
                doesn't bump the version every time
 20:48 < silbe> but maybe we should try to enforce the version some (other)
 way, instead of
                working around it in Journal
 20:48 < silbe> i guess collaboration uses the version number as well in
 some way?
 20:49 < tomeu> silbe: it should but doesn't afaik
 20:50 < tomeu> silbe: the issue of identity of an activity bundle is a
 tricky one
 20:50 < silbe> tomeu: we could go the git way and use the hash of the
 contents
 }}}

 The attached patch will stop Sugar from installing the bundle if the
 version number of the already-installed activity matches the one from the
 bundle.
 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.

-- 
Ticket URL: <http://dev.sugarlabs.org/ticket/1053>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list