-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24-01-10 08:06, Denys Dmytriyenko wrote: > On Sat, Jan 23, 2010 at 09:06:13PM +0100, Paul Menzel wrote: >> does [1] still describe the official policy to add checksums? Or is > > No > >> putting them into the recipes preferred nowadays? > > Yes
I think not! The new format: * is not documented * it has no tools to autogenerate it * has not been agreed on in any way. As an experiment I tried to use it for a branch at work and I *absolutely* hate the workflow needed for the new format. With checksums.ini it's a matter of: either cat /OE/tmp/checksums.ini >> conf/checksums.ini ; python contrib/source-checker/oe-checksum-sorter -i conf/checksums.ini or Verbatimly copy/paste the *output* OE gives you into conf/checksums.ini. These concerns have been raised time after time and still haven't been addressed, so for now: checksums.ini is the way to go -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFLXCEkMkyGM64RGpERAsSuAKCL8RKc/w03gNou79d3HXJbf8wqtACgnkrn 0jZ/RL/sSIoBxyLT4vGaMdc= =K1O3 -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
