Jean McCormack wrote: > Karen Tung wrote: > >> Jean McCormack wrote: >> >>> Jack Schwartz wrote: >>> >>> >>>> Another idea for your consideration: >>>> >>>> change the manifest spec. There is a >>>> <base_include type="file"> type of entry. We could introduce a >>>> <base_include type="uncompress_file"> type of entry. Then >>>> bootroot_initialize could make a list of files which shouldn't be >>>> compressed based on this, and can pass that file to bootroot_archive >>>> for proper handling. >>>> >>>> >>> I really like this solution and it works in with what is in the code. >>> Instead >>> of the filelist we use the manifest. >>> >>> Jean >>> >>> >> Hi Jean, >> >> I am confuse about what you mean by the "filelist we use in the >> manifest"? >> Which filelist are you talking about? >> > Not the filelist in the manifest but instead of using the > filelist.ramdisk to determine what to uncompress, > we'd use the manifest. Sorry for the confusion. > > Jean > > Hi Jean,
I think we should continue to use the filelist.ramdisk, then, whatever we specify in the manifest will be added to the filelist.ramdisk list. The reason for using filelist.ramdisk is that this is the list of file regularly maintained and updated by project teams that deliver into ON. Since we don't want to get into the business of trying to keep the list in our manifest consistent with the list delivered by ON, I think it is best to use the latest and greatest list from the build we are constructing the image for, then, add the few files that need not be compressed for our purpose. Thanks, --Karen
