Heiko Baums wrote: > Am Sun, 03 Dec 2017 09:53:21 +0000 > schrieb Peter Humphrey <pe...@prh.myzen.co.uk>: > >> On Sunday, 3 December 2017 04:15:25 GMT Heiko Baums wrote: >> >>> Like I said before. emerge always calculates the dependency tree, >>> which is a lot faster in case of `emerge -e @world` than in case of >>> `emerge -uDN @world`. And then it knows which packages have already >>> been installed and which are not. >>> >>> That said I haven't run an `emerge -e @world` before. So I'm >>> actually not sure if this works the same way as with an `emerge >>> -uDN @world`. >> Nope. Empty-tree means empty-tree. That is, whenever you emerge -e >> world, you start from the beginning every time, regardless of >> anything you were doing just before that. > Actually I was talking about the behavior of `emerge --resume` in the > case of `emerge -e @world` compared to `emerge -uDN @world`. Sorry, if > this was unclear. > > Heiko > >
I think I get what you are saying. If for example you start a emerge -e world, a emerge -uDN world or something and then stop it before it finishes, running emerge --resume should pick up where you left off. In the past, I have done that after a reboot. I'm not sure if having some things on tmpfs has a effect on that tho. That said, if you start one of those commands, emerge -e world for example, and then do some other command besides --resume, then most likely that will clear whatever emerge was doing before which means --resume won't work because it has been reset/cleared with the second command. As a workaround, I have been known to go to another terminal/konsole and do a emerge --resume -a and let it get to the point where I need to hit "y" and enter. I let it sit there and go back to the original terminal and emerge with whatever options I need for whatever package needs attention. Then when I'm done, I go to the other terminal/konsole and tell emerge yes to the --resume command. Once that command figures out what it needs to do, it already has its list to work with. However, I can emerge something in another terminal to fix things and hopefully carry on with the --resume. Sometimes doing that doesn't work but it could be worth a try. It's been a while since I've had the need to do that too. Generally, if a package fails, it will fail until something is fixed so that in can complete the process. As I've said before, emerge and how it does things has come a long ways in recent years. I hope I understood what you meant with all this. I disturbed quite a few electrons and stuff with this. lol Dale :-) :-)
