Well, I hope not. I still don't fully understand what is happening with the libpng/libpng3 business, but I strongly suspect the following scenario. You ask fink to install "foo" and it also requires "bar" so fink is going to install both at once. Let's say foo depends on libpng3 and bar depends on libpng. What does fink do? 1) First loads libpng3 because thats what foo wants 2) Next loads libpng because thats what bar wants 3) Successfully compiles bar, linked to libpng. 4) Manages to compile foo, with libpng still installed, because the dependecies are not checked a second time just prior to building.
Yup, I'm pretty sure that's how it's triggered. That also supports the fact that a rebuild of the offending package usually puts it right as well.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
