In some packages, you can use a flag to the "configure" step to disable
linking certain libraries. If that is possible, and you want to do it,
then you don't need to make the library a dependency.
However, if the library will be used whenever it is found and there is
no way to disable that, then
On Friday, January 31, 2003, at 04:51 PM, James Gibbs wrote:
If I am creating a package and the program adds features if compiled
with library N, should I automatically make it a build dependency?
It should be a dependency, yes. We try to make packages produce the
same thing on every platform
If I am creating a package and the program adds features if compiled
with library N, should I automatically make it a build dependency? Or
should I leave it for the user to decide how it should be compiled? For
example, if my software can read png, jpeg, and tiff if compiled with
their libs, sh
