From owner-freebsd-ports Fri Jan 29 15:04:22 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26983 for freebsd-ports-outgoing; Fri, 29 Jan 1999 15:04:22 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26978 for ; Fri, 29 Jan 1999 15:04:20 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-200.ix.netcom.com [209.109.235.200]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA08482; Fri, 29 Jan 1999 15:04:12 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.1/8.6.9) id PAA74817; Fri, 29 Jan 1999 15:03:52 -0800 (PST) Date: Fri, 29 Jan 1999 15:03:52 -0800 (PST) Message-Id: <199901292303.PAA74817@silvia.hip.berkeley.edu> To: sgk@troutmask.apl.washington.edu CC: freebsd-ports@FreeBSD.ORG In-reply-to: <199901292056.MAA32977@troutmask.apl.washington.edu> (message from Steve Kargl on Fri, 29 Jan 1999 12:56:14 -0800 (PST)) Subject: Re: Rationale for moving *.port.mk to Mk? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Steve Kargl * Date: Fri, 29 Jan 1999 12:56:14 -0800 (PST) * * Can someone explain the rationale for moving *.port.mk files * to ${PORTSDIR}/Mk? * * The Makefiles under the FreeBSD src tree do not include a target * to update these files. There appears to be no way to have these * files updated with a "make world". That's the way it's supposed to be. The port .mk files are supposed to be synchronized more with the ports tree, not the source tree. If you cvsup ports, then they will be updated automatically. By the way, anyone out there who's cvsupping ports *and* not getting the Mk files -- add "ports-base" to your cvsupfile, that is one collection you definitely don't want to miss as it includes all the toplevel files. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message