At 20:14 Uhr +0100 12.01.2003, Michel Schinz wrote:
Yeah indeed. IN fact dlopen is the most prominent example I think, and there have been several cases in the past with the same problem (I am guilty, too :-)"David R. Morrison" <[EMAIL PROTECTED]> writes:Just to clarify the situation a bit more: If the software you are packaging makes use of the Fink package foo whenever foo is present, and if you have no way to disable it from making use of foo, then you must list foo as a dependency.Yes, I realise that. The only problem is that until now I hadn't seen "dlopen" as a package... I think it's pretty easy to find dependencies when they are big. Say, you have a package which uses libpng if it finds it, and simply refuses to handle PNGs otherwise (but still handles other image formats). That's a pretty clear dependency, one which is likely to be documented, and one for which you certainly get a big warning at the end of the configure script. I just need to learn that dependencies on other packages can be really subtle. Basically every function whose existence is tested by the configure script could potentially be a dependency, now or in the future. That said, I think that in practice there are few such functions.
Luckily, a lot of stuff depends on dlcompat, reducing the probability that anybody runs into the problem.
Cheers,
Max
--
-----------------------------------------------
Max Horn
Software Developer
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
