On Wed, Nov 11, 2009 at 7:06 AM, Andrea Adami <[email protected]> wrote: >>>There was some discussion around alternative proposals of storing the >>> checksums in separate files within the recipes/ directory. > >>> The best alternatives so far where: >>> - Place the checksums into the dir of the recipe >>> - Use a MD5SUM_${URL} = "", SHA256SUM_${URL} = "" syntax >> >> I would be happy with the latter of those suggestions. I don't think >> the former really addresses the problems with the current checksums.ini. > > Yes, I sponsor the idea of a single Manifest in each dir. > > Let apart filetype specifier, example here: > http://www.gentoo.org/proj/en/glep/glep-0044-extras/manifest2-example.txt > > Having a Manifest listing the filename, the size and some checksums on > a single line seems to me very easy to parse for an automated script > wich could refresh/generate the whole file.
I also like the way Gentoo handle with this problem, but I guess that if we go that way we'd still have trouble regarding merging and conflicts, like we current have with checksums. Adding the checksum metadata in the recipe itself makes easier the life of a lot of people, we just need to identify the easier and prettier way of doing that. Cheers, -- Ricardo Salveti de Araujo _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
