Date: Fri, 29 Jan 1999 15:10:15 -0800 (PST) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: asami@FreeBSD.ORG (Satoshi Asami) Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Rationale for moving *.port.mk to Mk? Message-ID: <199901292310.PAA40676@troutmask.apl.washington.edu> In-Reply-To: <199901292303.PAA74817@silvia.hip.berkeley.edu> from Satoshi Asami at "Jan 29, 1999 3: 3:52 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Satoshi Asami wrote:
> * From: Steve Kargl <sgk@troutmask.apl.washington.edu>
> * 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.
This seems logical in that ports and src are differnt moving targets.
> 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.
But, ports-base includes a lot of stuff that a normal user does not
need to either build a port or start a new porting effort. You
only need the files under Mk.
ports-Mk?
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901292310.PAA40676>