[Bugs] #620 URGE: Cannot Erase activities installed in /usr/share/sugar/activities

[SugarLabs Bugs]

#620: Cannot Erase activities installed in /usr/share/sugar/activities
-----------------------+----------------------------------------------------
    Reporter:  wadeb   |          Owner:  sdz                        
        Type:  defect  |         Status:  closed                     
    Priority:  Urgent  |      Milestone:  Unspecified by Release Team
   Component:  SoaS    |        Version:  0.84.x                     
    Severity:  Major   |     Resolution:  wontfix                    
    Keywords:          |   Distribution:  SoaS                       
Status_field:  New     |  
-----------------------+----------------------------------------------------
Changes (by sdz):

  * priority:  Unspecified by Maintainer => Urgent


Comment:

 Replying to [comment:5 garycmartin]:
 > If we're really going to stick with a sub-set of Activities that no
 (normal) user can erase or upgrade, we should at leased file a critical
 blocker against the Sugar component for either an alert message if a user
 attempts to erase a locked activity, or that the erase palette option is
 disabled (greyed out) for root locked activities. Not too sure where
 warnings should go when a user blocked from upgrading a root locked
 Activity. What do others think?

 You can just run 'yum remove {put the name of the activity you want to get
 rid of here}', but for that, you need obviously root. +1 for the message
 thing - I like the greyed out solution even better. But in this case, this
 is urgent, as we're quickly approaching our deadlines for the SoaS beta
 release.

 A last point: Ideally, users should be able to get the latest activity as
 a RPM, but that's just not always the case.

-- 
Ticket URL: <http://dev.sugarlabs.org/ticket/620#comment:7>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system