On Wednesday 11 November 2009 09:24:09 Phil Blundell wrote: > On Wed, 2009-11-11 at 02:06 +0100, Holger Hans Peter Freyther wrote: > > SRC_URI = "http://example.org/${PN}-${PV}.tar,bz2" > > > > how do you want to handle these? What happens if you place a checksum in > > the inc file? Do you want to propose removing SRC_URI from .ini files and > > put them back to the .bb files? > > SRC_URI = "http://example.org/${PN}-${PV}.tar,bz2;md5sum=${MD5SUM}" > > You can define ${MD5SUM} whereever you like.
This will create an even bigger mess. Sometimes you need to download two things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM, B_SHASUM. The main problem with the above is that in contrast to a well defined checksums.ini file we will end up with n-variants of the above trick. I agree that conceptually the checksum belongs to the URI, but putting it into the URI is just creating a horrible mess. It has issues with .inc files, adding a shasum will make the URI not fit in any terminal... The best alternatives so far where: - Place the checksums into the dir of the recipe - Use a MD5SUM_${URL} = "", SHA256SUM_${URL} = "" syntax z. _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel