httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: [vote] release httpd-2.2.14?
Date Thu, 24 Sep 2009 12:38:49 GMT
Guenter Knauf wrote:

> the checksums are in wrong format. We need to commonly agree how to
> generate checksum files. The documented format what the user expects is:
> 
> # cat httpd-2.2.14.tar.bz2.md5
> a5226203aaf97e5b941c41a71c112704 *httpd-2.2.14.tar.bz2
> # cat httpd-2.2.14.tar.bz2.sha1
> eacd04c87b489231ae708c84a77dc8e9ee176fd2 *httpd-2.2.14.tar.bz2

Can you point out where this is documented?

Having dug into this further, there seems to be no standard format for
these files.

In the roll.sh script, an attempt is made to use md5sum if it exists,
falling back on openssl's md5 if md5sum doesn't exist on that platform
(md5sum doesn't exist on MacOSX).

> I create these on Linux and Win32 with a shell / batch script:
> #!/bin/sh
> test -z "$1" && echo "Usage: ${0##*/} <file>" && exit
> md5sum -b ${1} > ${1}.md5
> sha1sum -b ${1} > ${1}.sha1
> 
> @echo off
> if (%1)==() goto END
> md5sum -b %1 > %1.md5
> sha1sum -b %1 > %1.sha1
> :END
> 
> The huge benefit of this format is that the binaries can then be checked
> with same tools (option -c).

With the downside that what you propose only works on Linux.

Regards,
Graham
--

Mime
View raw message