Date: Wed, 29 Aug 2001 22:39:37 -0500 From: Steve Price <steve@FreeBSD.ORG> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Maxim Sobolev <sobomax@FreeBSD.ORG>, ports@FreeBSD.ORG, arch@FreeBSD.ORG, Alexander Langer <alex@big.endian.de> Subject: Re: ports.conf Message-ID: <20010829223937.Q56784@bsd.havk.org> In-Reply-To: <XFMail.010829142841.jhb@FreeBSD.org>; from jhb@FreeBSD.ORG on Wed, Aug 29, 2001 at 02:28:41PM -0700 References: <3B8CDC38.EC1EE32C@FreeBSD.org> <XFMail.010829142841.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 29, 2001 at 02:28:41PM -0700, John Baldwin wrote: > > Also, ports/Mk/ports.conf can easily just be a default file with everything > commented out that doesn't even get included. Rather, if a user wants to > customize, they create a /etc/ports.conf with teh appropriate knobs set, and > bsd.port.mk just includes /etc/ports.conf. The reason for putting the default > ports.conf in ports/Mk (or ports/defaults?) instead of /usr/share/examples or > some such is the same reason the ports makefiles are in ports/Mk and not > /usr/share/mk: it needs to be in sync with the ports tree. Like /etc/defaults/make.conf is always in sync with 'make world'? -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010829223937.Q56784>