On Sep 20 2004, at 08:45 Uhr, Stefano Franchi wrote:
I am try to execute a 'fink update-all' command that ends up in wanting to install/update 411 packages. After a few hours spent downloading all of them and then compiling about 1/3 of them, the command fails and exits when the compilation of [[insert package x here]].
(The discussion got side-tracked by information about fixing package x. Back to the question:)
I've run into the same problem often enough.
Would it be hard to have "fink update-all" randomize the sequence of updates it attempts?
Then the next fink update-all would be able to compile some other package.
Even better would be a "make -k" like function that just continues.
(This would be even more useful if there was a way to preserve the error information, but that's strictly optional.)
Why that would make a difference?
After a month or so of non-updating, it can easily take 24-48 hours to compile all the updates.
Obviously, this is good nighttime work for the box.
Getting stuck at a random package in the middle of the night is wasting the rest of the night.
Gruesse, Carsten
PS.: Another great thing would be some unattended way of getting all the downloads, but that's second priority.
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
