This is the expected behavior. Something in how our lynx package builds relies on behavior from a system utility that differs between the built-in version and that from coreutils-default. (I haven't looked at it, but it might be possible to do something different here, such as to include full paths so that things like "mv", "cp", and "install" are guaranteed to be the system's version). After lynx is built there is no such conflict.
As the message says, coreutils-default will be removed while lynx is built, and then reinstalled afterwards. If there's a build failure, coreutils-default will still be reinstalled. Basically you just won't have coreutils-default while you're building lynx. José H. Espinosa wrote: > Hey Luis, > > I have never seen this message before, but my filling is that you can > go ahead and temporally remove that package. I' cc'ing the fink- > users mailing list, they might be able to give you a better answer. > > Thanks, > Jose > > On Mar 26, 2009, at 9:06 AM, Luis Benet wrote: > > >> Hi, >> >> I just tried to update all my installation of fink. At some point, >> while updating >> the lynx package, I got the following message >> >> The following package will be installed or updated: >> lynx >> The following package might be temporarily removed: >> coreutils-default >> >> I answered NO because it seemed to me too that the message was >> awkward. Is the normal procedure? If something fails, what does it >> happen if I accept to "temporarily remove coreutils-default"? >> >> Thanks for your help, >> >> Luis >> >> > > > ------------------------------------------------------------------------------ _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
