Dealing with options in dependent ports

Emanuel Haupt ehaupt at
Fri Nov 30 16:05:07 UTC 2012

Thierry Thomas <thierry at> wrote:
> Hello,
> Le ven 30 nov 12 à 16:36:32 +0100, Paul Schmehl
> <pschmehl_lists at> écrivait :
> > 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.
> > 
> > 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?
> > 
> 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.
> -- 
> 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.


More information about the freebsd-ports mailing list