configure: Check that checksum programs produce correct checksums. + bitter rant
So, it might be called sha1sum, or on some other OS, it might be called sha1. It might be hidden away off of PATH on that OS. That's just expected insanity; UNIX has been this way since 1980's. And these days, nobody even gives the flying flip about standards that we briefly did in the 90's after the first round of unix wars. But it's the 2010's now, and we've certainly learned something. So, let's make it so sometimes sha1 is a crazy program that wants to run as root so it can lock memory while prompting for a passphrase, and outputting binary garbage. Yes, that'd be wise. Let's package that in major Linux distros, too, so users can stumble over it.
This commit is contained in:
parent
e36e54884e
commit
9cdbfa764e
4 changed files with 37 additions and 15 deletions
1
debian/changelog
vendored
1
debian/changelog
vendored
|
@ -21,6 +21,7 @@ git-annex (3.20121018) UNRELEASED; urgency=low
|
|||
does not accept that.
|
||||
* bugfix: Don't fail transferring content from read-only repos.
|
||||
Closes: #691341
|
||||
* configure: Check that checksum programs produce correct checksums.
|
||||
|
||||
-- Joey Hess <joeyh@debian.org> Wed, 17 Oct 2012 14:24:10 -0400
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue