Alexander K. Hansen wrote:
[]
What's interesting here is that on the first run the build conflict
wasn't able to be resolved automatically, but the auto-resolution did
work on the second run
In any case you can remove it. If you actually needed it as a
dependency Fink would complain when you remove it (which it won't), and
you're free to install it after openoffice.org is done, since this is a
_build_, not runtime, conflict.
And if everything goes smoothly, or even it there is a crash with a
clean exit, at the end fink will reinstall the package that it removed
before. The buildconflicts code is actually quite smart, but apparently
it is quickly exhausted, it doesn't seem to be good at handling more
than one build conflict at a time.
--
Martin
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
