From owner-freebsd-ports Fri Jan 29 14:40:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23870 for freebsd-ports-outgoing; Fri, 29 Jan 1999 14:40:38 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23851 for ; Fri, 29 Jan 1999 14:40:24 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.1/8.9.1) id OAA26884; Fri, 29 Jan 1999 14:40:18 -0800 (PST) (envelope-from mph) Date: Fri, 29 Jan 1999 14:40:17 -0800 From: Matthew Hunt To: Steve Kargl Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Rationale for moving *.port.mk to Mk? Message-ID: <19990129144017.B26710@wopr.caltech.edu> References: <199901292056.MAA32977@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901292056.MAA32977@troutmask.apl.washington.edu>; from Steve Kargl on Fri, Jan 29, 1999 at 12:56:14PM -0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 29, 1999 at 12:56:14PM -0800, Steve Kargl wrote: > This appears to be a gratuitous change? When you do a "make world", the /usr/share/mk/bsd.port.mk that is installed simply includes /usr/ports/Mk/bsd.port.mk. The idea is that when you cvsup the Ports Collection, bsd.port.mk will be kept in-sync with the ports. Previously, unsynchronized bsd.port.mk and POrts Collections were a major support issue. -- Matthew Hunt * Science rules. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message