Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Nov 2012 17:05:04 +0100
From:      Emanuel Haupt <ehaupt@FreeBSD.org>
To:        ports@FreeBSD.org
Subject:   Re: Dealing with options in dependent ports
Message-ID:  <20121130170504.7bc37b172743a934a7120bf5@FreeBSD.org>
In-Reply-To: <20121130154740.GA16360@graf.pompo.net>
References:  <A9F2CA034E76DB10EB615B3B@utd71538.campus.ad.utdallas.edu> <20121130154740.GA16360@graf.pompo.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Thierry Thomas <thierry@freebsd.org> wrote:
> Hello,
>=20
> Le ven 30 nov 12 =E0 16:36:32 +0100, Paul Schmehl
> <pschmehl_lists@tx.rr.com> =E9crivait=A0:
> > I'm working on a port that has an option for a build_depends on
> > another port.  If that option is selected, the dependent port MUST
> > be built with an option that is not selected by default.
> >=20
> > Is there a way to either force that option to be selected in the
> > dependent port?  Or, failing that, is it possible to pop up a
> > message warning the installer that they must select that option
> > before building the dependent port or, if they've already installed
> > it without the option, they must deinstall and reinstall after
> > selecting that option?
> >=20
>=20
> I'd suggest to make a slave port where you force the required option.
> However, to enforce the right dependency, this option have to produce
> a different plist.
> --=20
> Th. Thomas.

I was in the same situation with dns/ldns requiring python bindings
which are not built by default. I solved the problem by creating a stub
port dns/py-ldns.

Emanuel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121130170504.7bc37b172743a934a7120bf5>