David R. Morrison wrote:
I'm not sure that's the case. Since the deps are all indirect, isn't it possible to rebuild the packages that link libpng against libpng3 and the ones using libpng3 already would just work? The way the warning messages come out, it sounds like it's a runtime issue of loading 2 versions of the same library, not that the libpng3 app is somehow also getting libpng symbols at build-time...Sure. The problem is, how do we trigger the upgrade? We need to make sure that everything is *rebuilt* after upgrading, right? So does this mean a versioned dependency on anything linked against imlib, for example?
But yeah, if that is the case, we'd have to upgrade everything that touches it and force a versioned dep. Erg...
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
