"Pause" feature for emerge

[gspr]

I don't know if this has been proposed already, but wouldn't a pause feature for emerge be nice?
Take for instance upgrading the Xorg package, or some other intrusive upgrade. Wouldn't it be nice if one could pass a --pause to emerge that would cause it to stop just before copying in all the files from the image directory, and wait for user confirmation to procede? This would allow for users to for example exit Xorg before changes are actually made to the system.
_________________
"People said I should accept the world. Bullshit! I don't accept the world." -- RMS.
"We are to admit no more causes of natural things than such as are both true and sufficient to explain their appearances." -- Newton.

[adaptr]

This is not necessary - all emerge upgrades that do not require a restart to take effect are completely transparent.

If you want to implement this now just run emerge with --buildonly; this causes the binary package to be built but not merged.

To pause an emerge just pause it; ctrl-z to stop the process, fg to restart it.
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen

[BlackEdder]

I guess with completely transparent he means that you can savely leave xorg running while emerging xorg.

[russianpirate]

That is like saying can I use a new kernel when my old one is loaded.

[andrewd18]

That's right. The Unix filesystem is great that way... you can delete a file that's actually in use by a program, for example, an OOo text document. You can have it open in OOo, delete it with rm <filename>, and you can still make changes to it and save normally, in OOo.

Unix filesystems lock the file instead of removing it, so programs that already have it open can still modify it. Then, once no programs are using it, the file is completely removed.

So for example, you could upgrade X.org while running X.org... the old X.org build files will be locked, and then when you restart X, the old files will be unused (cuz the new one is now running), and within a few minutes, deleted.

~~ Andrew D.
_________________
Keep Your Toolchain Stable! - emwrap.sh

There's no place like ::1

[allucid]

[arnvidr]

[adaptr]

Not directly, but if you use ccache the already-processed bits will not take much time to compile.
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen

[ChojinDSL]

What would be really cool is if you could pause or hibernate an emerge, power off your pc, power it back on and then resume your emerge. Would be very useful in cases where something warrants a reboot, or if you had a laptop and need to unplug it for a while.

[GentooBox]

well, you could use the keepwork and keeptemp features of emerge.

just put in:

FEATURES="keepwork keeptemp"

in make.conf

normally when you emerge something, it will put the files into /var/tmp/portage/<name> and when you stop the merge and restart it, it will delete the /var/tmp/portage/<name> folder and unpack the files from the tar files.

but with keepwork and keeptemp, the files will be there when you restart the merge and it will not compile the "pre"-compiled files unless you changed useflags.

the downside is that the files will take up huge amount of space after a while, so you should delete the folders manually when not needed.
_________________
Encrypt, lock up everything and duct tape the rest

[arnvidr]

That won't do...at least for me. The only time I would need this if I can't let the computer sit and compile overnight, but the emerge isn't finished. I don't know how long it takes until after I've sync'ed anyway, and then I just go ahead no matter what...

[dundas]

[djh-world]

You could always use the handy GNU Screen.

Start the emerge in a screen session, then detach it, exit X then just re attach it.

No need for a pause.
_________________
djh-solutions :: freelance web design | solution provider

[djm]

Surely keepwork/keeptemp only affect what happens when an emerge exits successfully

If it fails, nothing gets deleted from $PORTAGE_TMPDIR

Afaik there's no way of stopping emerge --resume from starting the current package from scratch (I might be wrong though), but you can do ebuild /usr/portage/cat-egory/package/package-ver.ebuild merge, and the merge of the package will be completed without starting again.

However, packages won't be added to your world file if you do this (note: that only normally happens if it's something you explicitly emerged, and not if it's only emerged as a dep), so you can do emerge -n package to add the package to your world file without re-compiling it.

ebuild .. merge only does one package though - anything that was supposed to be merged afterwards you'll need to ask to be emerged again (you could do emerge --resume --skipfirst, fex)
_________________
the forums.gentoo.org poster formally known as metal leper

[peterton]

I know it's a bit of an old thread, but I thought I'd share my experiences anyway.
I wanted to build openoffice-ximian-1.3.16 on a machine which I couldn't leave powered on until the build was finished. I started the build like so: