#6497 NORM Never A: Current Activity-launch behavior makes Develop problematic

[Zarro Boogs per Child]

#6497: Current Activity-launch behavior makes Develop problematic
---------------------+------------------------------------------------------
  Reporter:  bemasc  |       Owner:  marco         
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  Never Assigned
 Component:  sugar   |     Version:                
Resolution:          |    Keywords:                
  Verified:  0       |    Blocking:                
 Blockedby:  6639    |  
---------------------+------------------------------------------------------

Comment(by homunq):

 Currently, Develop saves a backup copy in the journal when it starts to
 edit. Thus, there is always a way to go back to the original activity.

 However, the behaviour is worse than described in the bug description
 here. It only reinstalls/updates if the version number does not match. If
 you make a simple change and just want to test it, you attempt to launch
 the new version from the journal, but the version number matches, so it
 silently uses the previous version. This is very annoying (constantly
 changing the version number in activity.info) if you realize it, and would
 of course be even worse if you were trying to debug without realizing it.

 In my patched version of the journal, I have fixed #6639 but I have NOT
 fixed this, as I am not sure what the correct behaviour is.

 (one more thing - if the folder in Activities is actually a symlink, it
 fails by deleting the contents but not replacing them, leaving an empty
 folder. Solution: do not use symlinks.)

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