u-boot: Add sha256 hash value for earlier 2013.10 version.
PATCH 1/1 u-boot: Add sha256 hash value for earlier 2013.10 version.
Add a hash value for u-boot-2013.10.tar.bz2.
---
if i understand this correctly, if a package has no hash file, then
downloading generates a warning. but with the newly-added uboot.hash file, the missing sha256sum for the earlier 2013.10 version generates an "ERROR" when running "make source", even though the tarball is in fact downloaded correctly. so just add a hash value to quiet the download.
boot/uboot/uboot.hash +1 -0
@@ -1,2 +1,3 @@ # Locally computed: sha256 0a1a70df586655f527befa6f12e184e96ed61b126e5a567382321b17200f5d60 u-boot-2015.04.tar.bz2 +sha256 0d71e62beb952b41ebafb20a7ee4df2f960db64c31b054721ceb79ff14014c55 u-boot-2013.10.tar.bz2
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================PATCH 1/1 u-boot: Add sha256 hash value for earlier 2013.10 version.
Dear Robert P. J. Day,
Quoted 5 lines · Robert P. J. Day
Add a hash value for u-boot-2013.10.tar.bz2.
Signed-off-by Robert P. J. Day <[email protected]>
Quoted 8 lines
---
if i understand this correctly, if a package has no hash file, then
downloading generates a warning. but with the newly-added uboot.hash file, the missing sha256sum for the earlier 2013.10 version generates an "ERROR" when running "make source", even though the tarball is in fact downloaded correctly. so just add a hash value to quiet the download.
Nope, that's not the right way of doing things. First and foremost, a missing hash in the hash file is currently not a hard failure, only a warning. It will be turned into a hard failure soon, but with appropriate handling of custom versions (see the patch series being sent by Yann E. Morin and Arnout Vandecappelle about this).
The problem with your patch is that it adds just the hash file 2013.10. What about the dozens of other U-Boot releases? And the zillions of U-Boot forks all over the place?
Since it doesn't scale, we're going t keep it is simple: a hash for the default U-Boot version currently used by Buildroot, and that's it.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com