From owner-freebsd-ports  Wed May 28 19:40:51 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA18936
          for ports-outgoing; Wed, 28 May 1997 19:40:51 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA18931
          for <ports@freebsd.org>; Wed, 28 May 1997 19:40:49 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <18335(1)>; Wed, 28 May 1997 19:40:16 PDT
Received: by crevenia.parc.xerox.com id <177489>; Wed, 28 May 1997 19:40:08 -0700
From: Bill Fenner <fenner@parc.xerox.com>
To: ports@freebsd.org
Subject: MASTER_SITES=
Message-Id: <97May28.194008pdt.177489@crevenia.parc.xerox.com>
Date: Wed, 28 May 1997 19:39:56 PDT
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

For ports that we acknowledge are out of date and accept that the
master site no longer has the version of the files that we want (e.g.
hylafax, popclient), does it make sense to put an empty MASTER_SITES=
in the port Makefile?  This prevents the timeout or failed attempt to
get a file that we know for sure isn't going to get fetched, and forces
a fallback to the FreeBSD distfiles backup.

If the port does eventually get upgraded, the old MASTER_SITES= can be
resurrected from the CVS history if needed.

  Bill