From owner-freebsd-ports Tue May 2 12:36:45 2000 Delivered-To: freebsd-ports@freebsd.org Received: from patrol.area51.fremont.ca.us (adsl-63-195-147-14.dsl.scrm01.pacbell.net [63.195.147.14]) by hub.freebsd.org (Postfix) with ESMTP id A5CBC37BCE1; Tue, 2 May 2000 12:36:42 -0700 (PDT) (envelope-from mharo@patrol.area51.fremont.ca.us) Received: (from mharo@localhost) by patrol.area51.fremont.ca.us (8.9.3/8.9.3) id MAA49910; Tue, 2 May 2000 12:36:41 -0700 (PDT) (envelope-from mharo) Date: Tue, 2 May 2000 12:36:41 -0700 From: Michael Haro To: Satoshi - Ports Wraith - Asami Cc: FreeBSD Ports Team Subject: bsd.port.mk timeout idea Message-ID: <20000502123641.A49857@area51.fremont.ca.us> Reply-To: mharo@area51.fremont.ca.us References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from asami@FreeBSD.ORG on Tue, May 02, 2000 at 01:28:58AM -0700 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've thought about adding some sort of "timeout" in bsd.port.mk, so > users will have to upgrade their ports-base collection from time to > time, to ensure they will all have a reasonably new bsd.port.mk. What > do you guys think? What about having bsd.port.mk fetch a version file from the freebsd website and compare the versions reported. Maybe fetch/update this file every time a make fetch is done because I assume that when a make fetch is done that the user has access to the Internet. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message