From owner-freebsd-ports  Mon Feb 24 22:03:25 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA26816
          for ports-outgoing; Mon, 24 Feb 1997 22:03:25 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA26791
          for <ports@freebsd.org>; Mon, 24 Feb 1997 22:03:18 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vzFyq-00065w-00; Mon, 24 Feb 1997 23:03:12 -0700
To: ports@freebsd.org
Subject: make -k oddities
Date: Mon, 24 Feb 1997 23:03:12 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vzFyq-00065w-00@rover.village.org>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


When I do a make -k for a port that I don't have (and can't get) the
dist file for, then it will try to fetch and fail.  Once it fails it
will then try to patch, which it shouldn't do.

I'm running this on OpenBSD amd was wondering if others had seen this
problem or not on FreeBSD.  I've not tried it on FreeBSD due to
network pipe problems (that is, I need bigger ones).

I've also seen weird things where sometimes it would fetch things
twice, mysteriously hang when failing back to ftp.freebsd.org (but
only sometimes, and sometimes after < 64k was trasnferred) and a few
other sh related oddities.

If you've seen any of these things on FreeBSD, please let me know.
Otherwise, I think I have to assume that many of them are broken on
OpenBSD and be bummed.

Thank you for your time and efforts in this area.

Warner