From owner-freebsd-ports  Wed Feb 26 15:39:59 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA11410
          for ports-outgoing; Wed, 26 Feb 1997 15:39:59 -0800 (PST)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11405
          for <freebsd-ports@freebsd.org>; Wed, 26 Feb 1997 15:39:56 -0800 (PST)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.4/8.7.3) id PAA03965; Wed, 26 Feb 1997 15:39:12 -0800 (PST)
Date: Wed, 26 Feb 1997 15:39:12 -0800 (PST)
Message-Id: <199702262339.PAA03965@vader.cs.berkeley.edu>
To: adam@veda.is
CC: imp@village.org, freebsd-ports@freebsd.org
In-reply-to: <199702262008.UAA00718@veda.is> (message from Adam David on Wed, 26 Feb 1997 20:08:43 +0000 (GMT))
Subject: Re: make -k oddities
From: asami@vader.cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * We don't have FETCH_COOKIE, and if we did the dependency would cause make -k
 * to skip the build as expected.

This has nothing to do with cookies, Adam.  Look at the "fetch:"
target, and see how it returns 0 if "make -k" doesn't report failure.
Now look at the other targets (with my proposed patch), and see how
the cookies will be created anyway if "make -k" doesn't report
failure.

 * There must have been a good reason not to implement FETCH_COOKIE?

Yes.  ${WRKDIR} is not created at that point. :)

I didn't bother trying to work around that because invoking do-fetch
on an already-fetched set of distfiles in harmless (basically it will
just check the files are there and return 0).

Satoshi