Date: Wed, 29 Aug 2001 09:33:30 -0500 From: Will Andrews <will@physics.purdue.edu> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Alexander Langer <alex@big.endian.de>, arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf Message-ID: <20010829093330.T35352@bohr.physics.purdue.edu> In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Aug 29, 2001 at 03:12:40PM %2B0300 References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev (sobomax@FreeBSD.org) wrote: > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. This would solve "where to put it" and "at which > point to include it" problems. Comments? We already .include several things that could be used as a substitute for the hypothetical ports.conf, like $PORTSDIR/Makefile.inc or similar... -- wca 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?20010829093330.T35352>