Martin Costabel wrote: > Before you move this from experimental to unstable, I'd like to remind > you that with or without symlinks, this is *not* going to be compatible > with any old package, as long as you change the install_name of the > dylibs. I got bitten by this while I tried your experimental > qt3-3.3.6-22. If you change the install_name from > %p/lib/libqt-mt.3.dylib to %p/lib/qt3/lib/libqt-mt.3.dylib, you have to > change the package name, too, from qt3-shlibs to qt336-shlibs or something.
I figured that as long as things are upwardly-compatible, and it remains with the old shlibs for old packages, I didn't think I should have to change it. I can always fiddle with -install_name if I have to, but I didn't think I had to remain backwards compatible with old versions of my packages, that would be a maintainability nightmare. As long as you can continue using it going forward, I would have thought it would be OK. Although, I suppose we would have to change versioned deps on anything that wants Qt, if we wanted a bindist to be internally consistent. I guess I'll change the -libdir in configure :) -- Benjamin Reed a.k.a. Ranger Rick http://ranger.befunk.com/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
