From owner-freebsd-ports  Fri Sep 10  9:19:24 1999
Delivered-To: freebsd-ports@freebsd.org
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by hub.freebsd.org (Postfix) with ESMTP id EFD061587F
	for <ports@freebsd.org>; Fri, 10 Sep 1999 09:19:18 -0700 (PDT)
	(envelope-from fenner@research.att.com)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 1D7AE4CE0C; Fri, 10 Sep 1999 12:18:10 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA02242;
	Fri, 10 Sep 1999 12:18:08 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA26093;
	Fri, 10 Sep 1999 09:18:08 -0700 (PDT)
Message-Id: <199909101618.JAA26093@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: alex@cichlids.com
Subject: Re: Refetch for bsd.port.mk on checksum errors
Cc: ports@freebsd.org
Date: Fri, 10 Sep 1999 09:18:07 -0700
Versions: dmail (solaris) 2.2e/makemail 2.8u
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


That's a good idea when the checksum mismatch is because the port was
updated, but maybe doesn't work so well when it's because the port is
stale (since you will never get a checksum match and you will always
refetch).

  Bill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message