Date: Fri, 4 May 2001 14:31:41 -0500 From: Will Andrews <will@physics.purdue.edu> To: Eric Melville <eric@FreeBSD.org> Cc: FreeBSD Ports <ports@FreeBSD.org> Subject: Re: port policies Message-ID: <20010504143140.J3246@casimir.physics.purdue.edu> In-Reply-To: <20010504123304.B66630@FreeBSD.org>; from eric@FreeBSD.org on Fri, May 04, 2001 at 12:33:04PM -0700 References: <200104300810.f3U8AGY60114@freefall.freebsd.org> <86elua4wf1.wl@archon.local.idaemons.org> <20010430023347.A70094@xor.obsecurity.org> <20010504123304.B66630@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 04, 2001 at 12:33:04PM -0700, Eric Melville wrote: > Is it also accepted policy to NOT hardcode -j options to make? If not, can > we make it so? This is just asking for trouble in many cases. Sure. I think it's probably useful to add a "MAKE_JOBS" variable to bsd.port.mk so people who know what they are doing can use it easily. Regardless, I agree 100% with you on the -j thing. -- 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?20010504143140.J3246>