#9839 BLOC 1.5-sof: Buildsystem needs to create file manifest of build using md5deep

[Zarro Boogs per Child]

#9839: Buildsystem needs to create file manifest of build using md5deep
--------------------------+-------------------------------------------------
 Reporter:  rsmith        |                 Owner:  cjb               
     Type:  defect        |                Status:  new               
 Priority:  blocker       |             Milestone:  1.5-software-final
Component:  build-system  |               Version:  not specified     
 Keywords:                |           Next_action:  never set         
 Verified:  0             |   Deployment_affected:                    
Blockedby:                |              Blocking:                    
--------------------------+-------------------------------------------------
 As part of the run-in test we are going to use md5deep to check all the
 files on the system.

 So at build time we need md5deep run on the image and the resulting
 manifest saved in the filesystem.

 A new directory called /runin is probably a good place this but I'm open
 to other locations if someone thinks theres a better place.

 The command needed is md5deep -r -of <list of dirs> > filename

 you can then compress the manifest with gzip or lzma.  My tests showed
 that the manifest was 5 megs and compressed it dropped to 1.2meg or 1 meg
 depending on .gz vs .lzma

 I'm not sure if our versions system will mess this up but the above
 commands tells md5deep to only hash files. We may need to execute the
 shallow copy at build time.

 On that note the shallow copy at 1st boot was necessary because on XO-1
 the loop mounter for JFFS2 could not do softlinks.  This is not the case
 for X0-1-5.  Do we need still need to do the shallow copy at 1st boot or
 can we do it at build time?

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