#6470 NORM Never A: olpc-update doesn't let users manage their software builds

[Zarro Boogs per Child]

#6470: olpc-update doesn't let users manage their software builds
------------------------------+---------------------------------------------
  Reporter:  gnu              |       Owner:  cscott                           
      Type:  defect           |      Status:  new                              
  Priority:  normal           |   Milestone:  Never Assigned                   
 Component:  upgrade utility  |     Version:  Development build as of this date
Resolution:                   |    Keywords:                                   
  Verified:  0                |    Blocking:                                   
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by cscott):

 Please see the olpc-update and update_streams documentation in the wiki.

 The "cross-build" stuff is because your editor doesn't do the "write to a
 temp file and move" mechanism of editing files; it is editing them in
 place instead.  The hardlinked cow system can't protect you from that; you
 need to be careful instead.

 I've certainly got plans to implement a "real" cow system (help
 appreciated) but I've got other fires to fight at the moment.  We had a
 real cow system originally, but we had to abandon it when vserver proved
 not production-ready.

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