Date: Fri, 28 Nov 1997 16:31:48 -0500 (EST) From: Tim Vanderhoek <hoek@hwcn.org> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: hoek@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: patch to bsd.port.mk: >1 md5 hash per file Message-ID: <Pine.GSO.3.96.971128162056.14554B-100000@james.freenet.hamilton.on.ca> In-Reply-To: <199711280154.RAA02800@baloon.mimi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Nov 1997, Satoshi Asami wrote: > * It would be nice if the md5 hash for both versions of the file > * could be included in files/md5, even if the addition of the 2nd > * hash had to be done manually. > > * - elif [ "$$CKSUM" = "$$CKSUM2" ]; then \ > * + elif expr "$$CKSUM2" : ".*$$CKSUM" > /dev/null; then \ > > Oh, I see. At first I thought you were talking about adding two lines > for the same file, actually you mean something like > > MD5 (imaze.tar) = 6c042fe0afcc3399b31b25ce16d9fb3b/1cfac4f65653dbd2ed43f8e842a9a374 Actually, I think what you first thought was what I meant... :-) ie. MD5 (uudeview-0.5.13.tar.gz) = fda32e2de4a6b92eb56f1e286ae3815a MD5 (uudeview-0.5.13.tar.gz) = dddf4c01973307c7d203f55c5e0c7fc3 After the md5 file get sucked in, the shell normally turns all the \n's into spaces, but even if IFS, etc. are set so that the shell doesn't do this, "expr" should still find the right string (well, it did when I tested it, anyways :). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.971128162056.14554B-100000>