Date: Sun, 23 Dec 2007 08:32:56 +1100 From: Edwin Groothuis <edwin@mavetju.org> To: Josh Paetzel <josh@tcbug.org> Cc: freebsd-ports@freebsd.org Subject: Re: Opinion on cross-port OPTIONS CONFLICTS Message-ID: <20071222213255.GJ40969@k7.mavetju> In-Reply-To: <200712221150.59971.josh@tcbug.org> References: <200712211524.25454.josh@tcbug.org> <200712212105.21520.josh@tcbug.org> <20071222043344.GB82459@k7.mavetju> <200712221150.59971.josh@tcbug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 22, 2007 at 11:50:53AM -0600, Josh Paetzel wrote: > On Friday 21 December 2007 10:33:44 pm Edwin Groothuis wrote: > > On Fri, Dec 21, 2007 at 09:05:18PM -0600, Josh Paetzel wrote: > > > > > It also doesn't work if someone runs make rmconfig, or make config > > > > > again and changes things after the port is installed. > > > > > > > > > > It probably doesn't work if a package was used to install either. > > > > > > > > Create a slave port audio/arts-withoutnas and let it depends on > > > > that one. > > > > > > I don't think that's a scalable solution. It would create an explosion > > > of ports in the already taxed tree, as well as confusion as to which port > > > to install among the users. > > > > And what is your solution for this problem? > > My initial solution as I posted is to register the OPTIONs used to build a > port in /var/db/pkg And how is that going to resolve the issue earlier suggestions suffered from with regarding to ports which are not installed yet but which will be installed as a dependency of this port? Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071222213255.GJ40969>