peterjeremy at acm.org
Wed Apr 11 06:09:54 UTC 2012
On 2012-Apr-09 21:02:01 -0500, Stephen Montgomery-Smith <stephen at missouri.edu> wrote:
>So suppose we are building port A. It turns out that the configure in
>port A autodetects whether package B is present or not. It will build
>either way. But if built with package B, it will not operate without it.
>What are the accepted ways of handling this?
>1. Don't worry about it. tinderbox builds will never build port A in
>the presence of package B.
>2. Have the Makefile of port A detect whether package B is installed,
>and if it is then add B as a dependency of A.
>3. Cripple the configure in port A so that it doesn't autodetect for
Preference order is 3, 2, 1. 1 is the least desirable because the
resultant packages may include implicit dependencies without
explicit dependencies. It can also cause subtle problems when port
B is updated without updating port A.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120411/444393fc/attachment.pgp
More information about the freebsd-ports