LHerm wrote:
Fink within Fink Commander did a selfupdate and then an update-all that contained only ocaml and the four python packages listed below. Fink asked about uninstalling libquicktime0 and I responded yes. Ocaml was installed first. Sorry but I forgot to copy the first part of the log but I am sure that ocaml then reinstalled libquicktime0 as one of its dependencies. Python then tried to install but failed because of a conflict with libquicktime0. I ran Fink selfupdate again just in case something had changed and then did the update all again on the four python packages. Fink removed libquicktime0 again after asking. Python then installed without incident and Fink reinstalled libquictime0.
Yes, this is a known bug (I think there is an item on the bug tracker about it). The BuildConflicts code is too primitive to know when to reinstall a package it has removed. It removes everything at the beginning and then reinstalls it after the first package has been installed, regardless of which package actually asked for the removal. I suspect some of the people in the know think about this from time to time, but this is highly complicated stuff, so it may not be fixed very quickly.
-- Martin ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
