Thanks! Makes sense. I will fix committers/tools/signAndHash.sh and verifiySigs.sh to use use md5sum -b
Will also add the -b to example in release.html. -Phil On 12/17/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > From memory it came up a couple of times on the dev list, but I could only > find this: > > http://www.mail-archive.com/[email protected]/msg67770.html > > Niall > > ----- Original Message ----- > From: "Phil Steitz" <[EMAIL PROTECTED]> > To: "Jakarta Commons Developers List" <[email protected]> > Sent: Sunday, December 18, 2005 2:31 AM > Subject: [all] md5 checksum file formats > > > We seem to be converging on a "standard" (mentioned in > /releases/release.html as an ASF standard, but I can't find it > documented anywhere) for md5 checksum files that takes the form > > hash *<name> > > I am curious as to where the extra stuff comes from (i.e., why we > decided to add the * and the file name). Looking around apache, I > find > > httpd uses > hash <name> > (note no "*") > > ant, struts, tomcat, geronimo use > hash > > commons components are split between just having the hash and adding > on the "*name". > > It seems silly to me to add the extra contents, since this is just > duplicating the file name inside the file. Of course, I am sure there > is a good reason for this and I just don't know it, so maybe someone > can clue me in or point me to a link where this is documented? > > Thanks! > > Phil > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
