On Sun, 2010-04-25 at 10:48 -0700, Tom Rini wrote: > Hey all. I thought I would try and explain what Chris has been up to > There's a few ways out of this: > 1) Don't rely on 'cp' and 'md5sum' anymore but use python for it. > 2) Make an oe_cp and oe_md5sum to go with oe_sha256sum > 3) IIRC, the big part of coreutils-native was a fully functional, > always, 'install'. We could just copy the install we build or provide > an install wrapper (oe_install) or so > 4) ???
How about making the coreutils-native staging process be atomic, i.e. install binaries as cp.new (or whatever) and then do "mv cp.new cp"? Or, more generally I guess, arrange for new-style staging to do that for all binaries it installs. If (3) is sufficient then it seems like we might just as well exhume the old install-native package and ditch coreutils-native altogether. That would avoid the race since it doesn't install anything other than install. p. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
