From owner-freebsd-questions Sun Nov 1 11:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25833 for freebsd-questions-outgoing; Sun, 1 Nov 1998 11:56:08 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dt053n18.san.rr.com (dt053n18.san.rr.com [204.210.34.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25824 for ; Sun, 1 Nov 1998 11:56:05 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053n18.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA01889; Sun, 1 Nov 1998 11:55:52 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <363CBCC8.1361A0EE@gorean.org> Date: Sun, 01 Nov 1998 11:55:52 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1101 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brett Taylor CC: Ben Smithurst , Tomer Weller , freebsd-questions@FreeBSD.ORG Subject: Re: bsd.port.mk References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brett Taylor wrote: > Man this is becoming a FAQ. So much so that we should seriously consider making updating the bsd.port.* files part of the ports upgrade process. Either move the necessary files under /usr/ports and include them in cvsup somehow, or just add updating them in place to one of the cvsup targets for ports. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message