Date: Mon, 11 Apr 2011 08:54:50 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/Mk bsd.ncurses.mk bsd.port.mk ports/audio/cmus Makefile ports/audio/ncmpcpp Makefile ports/audio/ocp Makefile ports/audio/pytone Makefile ports/deskutils/wyrd Makefile ports/devel/cdk Makefile ports/devel/stfl Makefile ... Message-ID: <20110411085450.GA82163@FreeBSD.org> In-Reply-To: <201104110834.p3B8YHDQ034678@repoman.freebsd.org> References: <201104110834.p3B8YHDQ034678@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 11, 2011 at 08:34:17AM +0000, Baptiste Daroussin wrote: > Add a new macro to deal with conflict between ncurses from base and ncurses > from ports. > If a ports is linked against ncurses from base or from the ports, it should > then add: > > USE_NCURSES=yes > > It is also possible to specify the hard dependency on the ports ncurses or > one the base one adding the following macros: > > WITH_NCURSES_PORT=yes or WITH_NCURSES_BASE=yes Hmm, maybe we could avoid polluting the namespace with these extra WITH_NCURSES_FOO knobs? Can it be just USE_NCURSES=[yes|base|ports] ? I believe WITH_OPENSSL also suffers from similar problem. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110411085450.GA82163>