#6317 HIGH Never A: olpc-update 656 disassociates external apps installed in previous build

[Zarro Boogs per Child]

#6317: olpc-update 656 disassociates external apps installed in previous build
----------------------+-----------------------------------------------------
  Reporter:  chihyu   |       Owner:  kimquirk      
      Type:  defect   |      Status:  new           
  Priority:  high     |   Milestone:  Never Assigned
 Component:  website  |     Version:                
Resolution:           |    Keywords:                
  Verified:  0        |    Blocking:                
 Blockedby:           |  
----------------------+-----------------------------------------------------
Changes (by adricnet):

 * cc: adricnet (added)


Comment:

 Some users have requested a way to install RPMs into a different location
 to avoid this.

 I have not gone so far as to suggest chroot, but I have told a few folks
 who I thought could use the information that if they wanted their
 installed software to stick around then they should put it in /home (or
 /opt ..) or on an SD drive and modify their PATH.
 Or get used to yumming in subversion everytime you olpc-update (which is
 what I'm doing, more or less).

 This is obviously well beyond the realm of normal support, but may
 function as a work around. Another idea is to retarget yum/rpm installs
 but I don't know enough RedHat to say how that could be done.

 Note: IMHO This bug really is a Feature. I'm not really qualified to
 explain the details, butI believe that Bitfrost will eventually use this
 and copy-on-write to implement the
 http://wiki.laptop.org/go/OLPC_Bitfrost#P_SF_CORE:_core_system_file_protection
 protection of system files. In short, you can 'get root' and make quite a
 mess but will still be able to reboot into a running system. It's not
 fully implemented yet, afaik. If someone with $clue could correct me
 please ?

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