ports, dependencies and conflicts with other ports' options ?

Thierry Thomas thierry at FreeBSD.org
Sun Jan 10 21:29:46 UTC 2016

Le dim 10 jan 16 à 21:51:23 +0100, Kurt Jaeger <lists at opsec.eu>
 écrivait :

> Hi!


> There's a PR for a new port, see
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202754
> which has the problem that if some other port has some option
> set, this will cause this new port fail on build.
> So the question is: Is there any idea on how one might
> document / encode this kind of CONFLICT ?
> I'm pretty sure there's no mechanism in place right now,
> any ideas on a mechanism that would cover this ?

Next releases of pkg should support flavors, but in the meantime, I
would suggest to create slaves ports with the conflicting options
disabled, and then depend on these ones.

Th. Thomas.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20160110/398d13ae/attachment.sig>

More information about the freebsd-ports mailing list