Daniel Macks <[EMAIL PROTECTED]> wrote: > On Sat, Feb 26, 2005 at 03:21:30PM -0500, David R. Morrison wrote: > > Actually, Justin, buildconflicts *had* been working recently. But as Martin > > points out, the buildlock system has now broken it. > > That seems strange. In Engine.pm, the calls to *_buildlock are tightly > wrapped around the phase_* calls that build the package. All of this > is well *inside* the lines documented to: > # remove buildconfilcts before new builds reinstall after build > and > # Reinstall buildconficts after the build > > dan >
OK, I've done some experimenting and I understand this better now. Buildconflicts still works in 0.24.0, and was not broken by buildlock. If you have a package with "Buildconflicts: foo-dev", and foo-dev is installed when you try to build it, fink will still ask you if you want to remove foo-dev at the beginning of the process (and will refuse to proceed if you say no). The problem arises in the middle of a big compile of lots of packages. If foo-dev gets installed in the middle of the process, then there is no longer an opportunity to remove foo-dev, and the buildlock (correctly) interrupts the process when the buildconflicts is encountered. Even though this is correct behavior, it can be difficult for users to understand what's happening. I think we need better error messages for this situation, and I'll work on writing some. -- Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
