From owner-freebsd-ports  Wed Jul 12 16:10:15 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5C39737BFE5; Wed, 12 Jul 2000 16:10:08 -0700 (PDT)
	(envelope-from asami@cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca14-12.ix.netcom.com [205.186.215.12])
	by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA10229;
	Wed, 12 Jul 2000 19:10:01 -0400 (EDT)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id QAA73199; Wed, 12 Jul 2000 16:09:55 -0700 (PDT)
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Ben Smithurst <ben@FreeBSD.org>,
	Will Andrews <andrews@technologist.com>,
	Neil Blakey-Milner <nbm@mithrandr.moria.org>,
	Adam <bsdx@looksharp.net>, ports@FreeBSD.org
Subject: Re: fetch(1) timeout
References: <xzpvgyb65g1.fsf@flood.ping.uio.no> <20000712055707.C1690@argon.gryphonsoft.com> <xzpn1jn64r2.fsf@flood.ping.uio.no> <20000712061459.D1690@argon.gryphonsoft.com> <xzpitub63in.fsf@flood.ping.uio.no> <20000712064405.E1690@argon.gryphonsoft.com> <xzpem4z62n0.fsf@flood.ping.uio.no> <20000712065724.F1690@argon.gryphonsoft.com> <20000712131725.A23242@mithrandr.moria.org> <20000712072043.H1690@argon.gryphonsoft.com> <20000712153329.I11000@strontium.scientia.demon.co.uk> <xzppuojl4by.fsf@flood.ping.uio.no>
From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
Date: 12 Jul 2000 16:09:55 -0700
In-Reply-To: Dag-Erling Smorgrav's message of "12 Jul 2000 18:07:45 +0200"
Message-ID: <vqcaefnaqt8.fsf@silvia.hip.berkeley.edu>
Lines: 17
X-Mailer: Gnus v5.7/Emacs 20.7
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

 * From: Dag-Erling Smorgrav <des@flood.ping.uio.no>

 * 2) the file is not deleted if the transfer times out or is
 *    interrupted, but this is actually a bug.

Sorry, bsd.port.mk can't cope with -r.  If a file is left behind from
an aborted transfer, bsd.port.mk will see it and won't call fetch --
it will just go ahead and bomb in checksum.  This is a feature.

The problem is that bsd.port.mk cannot tell if a file is a result of
an aborted transfer.  (Humans can, but not a script.)

Even if it somehow tried, you might get connected to a different
master site the second time around.  What will happen if -r is
specified?

Satoshi


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