From owner-freebsd-ports  Fri Aug 18 02:19:38 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id CAA11424
          for ports-outgoing; Fri, 18 Aug 1995 02:19:38 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id CAA11416
          for <ports@freebsd.org>; Fri, 18 Aug 1995 02:19:33 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id CAA04199; Fri, 18 Aug 1995 02:18:21 -0700
Date: Fri, 18 Aug 1995 02:18:21 -0700
Message-Id: <199508180918.CAA04199@silvia.HIP.Berkeley.EDU>
To: gary@palmer.demon.co.uk
CC: jhs@vector.eikon.e-technik.tu-muenchen.de, ports@freebsd.org
In-reply-to: <149.808459398@palmer.demon.co.uk> (message from Gary Palmer on Tue, 15 Aug 1995 05:03:18 +0100)
Subject: Re: bsd.ports.mk checksum
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@freebsd.org
Precedence: bulk

 * I'm not sure how this ever became the case, it certainly was never my

It changed when the targets got all chained up, because everything
eventually depends on checksum.

 * Also, once the port is extracted, there is not much the current system
 * can do about mis-matches, apart from gripe, which is kinda pointless
 * IMHO.

Hmm, I thought that (gripe) was the whole point.  That's all it can do 
anyway!

This is the logic: if the checksum in the files/md5 is different, that
means files/md5 is updated after the distfile, which means the other
support files (Makefile, patches, package files, etc.) are updated
too, so it's no longer valid do to anything at this port (whether it's 
already extracted or not).

Satoshi