iThink that the issue of upgraded fink installs is the primary problem in fink, and without the question of backward compatability it would be a) easier to improve b) easier to fix and c) better. The dlcompat library doesn't get linked correctly because there are binary packages on the upgraded system that look for the wrong one, the freetype2 stuff is the same, its all because people have upgraded, its obviously not an issue if its all new. Also, there are packages that are fine to be rebuilt in panther after an upgrade, but other packages that depend on those may also upgrade but the combination won't work if one, but not the other, is upgraded in the wrong order. We had the issue of upgrading after the xfree 4.3 release etc etc etc etc blah...

There should be a "forced" upgrade path, where everything *must* be rebuilt, IN ORDER OF DEPENDANCY, that is installed. Perhaps, just a forced re-bootstrapping of fink (with he old tree moved out of the way, ENTIRELY) that then rebuilds all installed packages (or apt-get's in case of a binary install). This is the only way to fix things like this, without "special hacks" like dummy packages, weird "virtual packages" and even things that screw with the build system like the custom freetype2.la that was mentioned.

iKnow that this isn't the best user experience, but if its presented in the right way, then it will end up with a much better experience sine things won't break (as much)!

JP





--
"NOTICE: This E-mail (including attachments) is covered by the Electronic
Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution or copying of this communication is strictly prohibited, Please reply to the sender that you have received the message in error, then delete it. Thank you."

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to