Opinion on cross-port OPTIONS CONFLICTS

Edwin Groothuis edwin at mavetju.org
Sat Dec 22 13:32:59 PST 2007


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 at mavetju.org    |              Weblog: http://www.mavetju.org/weblog/


More information about the freebsd-ports mailing list