Date: Wed, 11 Apr 2012 16:09:37 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: Stephen Montgomery-Smith <stephen@missouri.edu> Cc: freebsd-ports@freebsd.org Subject: Re: autodetecting dependencies Message-ID: <20120411060937.GA62949@server.vk2pj.dyndns.org> In-Reply-To: <4F839499.8050103@missouri.edu> References: <4F839499.8050103@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Apr-09 21:02:01 -0500, Stephen Montgomery-Smith <stephen@missouri.e= du> wrote: >So suppose we are building port A. It turns out that the configure in=20 >port A autodetects whether package B is present or not. It will build=20 >either way. But if built with package B, it will not operate without it. =2E.. >What are the accepted ways of handling this? > >1. Don't worry about it. tinderbox builds will never build port A in=20 >the presence of package B. > >2. Have the Makefile of port A detect whether package B is installed,=20 >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=20 >package B. 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. --=20 Peter Jeremy --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk+FICEACgkQ/opHv/APuIfWGACfcS9edoYHBZ2ZprJUm8SN84/c WTYAn0wqN2bDsnb5fflqfLSRdImF9Tl5 =80f4 -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120411060937.GA62949>