Date: Sat, 16 Jan 2010 10:13:29 -0600 From: Kirk Strauser <kirk@strauser.com> To: glarkin@FreeBSD.org Cc: Craig Whipp <crwhipp@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Dislike the way port conflicts are handled now Message-ID: <4B51E5A9.4060303@strauser.com> In-Reply-To: <4B51473F.90302@FreeBSD.org> References: <4B509B51.3060809@strauser.com> <85E67FE7-4B01-40D0-A52E-BE8F3F083FAA@gmail.com> <4B51473F.90302@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/15/2010 10:57 PM, Greg Larkin wrote: > This change was based on a recent PR > (http://www.freebsd.org/cgi/query-pr.cgi?pr=137855) and made it into the > tree a couple of weeks ago: > http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?r1=1.631;r2=1.632 > > Since some folks like the old behavior and some folks like the new > behavior, what do you all think of a user-selectable make.conf option to > choose where the check-conflicts target appears in the port build sequence? > > Regards, > Greg > I'd love that. The new behavior isn't a bad default, but it needs an override. Wait a minute; rewind. Isn't that what "make -DDISABLE_CONFLICTS" does? -- Kirk Strauser
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B51E5A9.4060303>