On Mon, 30 Apr 2012 15:50:18 -0700, Mark Knecht wrote: > > I'm not sure what the big deal is, so portasge skips emerging one > > package because it can't download the distfile. So what? The previous > > version worked OK the day before and won't suddenly break because an > > update is available. Just download and upgrade when you have the > > time, casting the appropriate curses for those that set the licence. > > > > I agree. To me it's not much of an issue. However sometime ago when > there was a conversation about how people update their machines I > mentioned that I always do an > > emerge -fDuN @world
I do something similar, from a cron script that runs emerge --sync and a couple of other bits. > prior to kicking off the real emerge just to ensure that when the > build finally does start all the files are here and ready. This sort > of issue is precisely why I do that. This still isn't an issue, as long as you use --keep-going. The emerge world will proceed to update everything but the one affected package. > I know most people don't like calculating all the dependencies > multiple times but I prefer to do so, get the files and then pretty > much be guaranteed that the build proceeds without much attention from > me. It is a useful method of detecting potential problems, but this isn't really a problem. However, as my script emails me the output of emerge -p world (which means I actually calculate the dependencies three times, but I don't care as I'm asleep for the first two) I know about the fetch restriction as soon as I read my mail, and can decide whether to deal with it immediately or ignore it. -- Neil Bothwick Don't be humble, you're not that great.
signature.asc
Description: PGP signature
