#7713 NORM 8.2.0 (: Inconsitent behavior for activity installation

[Zarro Boogs per Child]

#7713: Inconsitent behavior for activity installation
----------------------+-----------------------------------------------------
   Reporter:  erikos  |       Owner:  tomeu               
       Type:  defect  |      Status:  new                 
   Priority:  normal  |   Milestone:  8.2.0 (was Update.2)
  Component:  sugar   |     Version:  Git as of bug date  
 Resolution:          |    Keywords:  8.2.0:?             
Next_action:  design  |    Verified:  0                   
  Blockedby:          |    Blocking:                      
----------------------+-----------------------------------------------------

Comment(by cscott):

 Replying to [comment:5 Eben]:
 > This is not true now?  The whole point of exposing the bundle directly
 in the Journal is to allow one to open a "clean instance" of the activity.
 What happens when you click on a bundle now, if it doesn't launch the
 activity?

 I was referring to the fact that currently the datastore maintains the .xo
 file (in packed form), while execution happens from
 ~/Activities/foo.activity (in unpacked form).  We have to do an
 installation/upgrade step in the datastore before we can "resume" the .xo
 entry in the datastore.

 I hope that we can run the activity directly from the .xo bundle (or,
 conversely, maintain the activity in unpacked form in the datastore) in
 the 9.1 timeframe.  This drastically reduces the space used when you try
 to install WikiBrowse, for example.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7713#comment:7>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system