On Tue, 06 Dec 2005 21:22:23 +0100, Holly Bostick wrote: > > The emerge -u invocation wasn't actually emerging anything, so it > > won't write to world. > > Yes, got that, but it would be scanning the world file to determine what > had updates available that had not been performed. If some of the > updates were at the same moment being performed in another instance, > that is not likely to confuse Portage as to whether an update to > konqueror (for example) was available or not (if konqueror was at that > moment being upgraded in the other console)?
I've often done emerge -u world in one console then done emerge -up world (sometimes piped to genlop -p) in another to see what's left to do. > > Emerging KDE only results in one write to world, at the end of the > > process. > > I suppose, if you're only emerging kde-meta (since all the sub-builds > are dependencies that will not be added to your world file. > > If I'm upgrading the split ebuilds, though.... does that remain the > case? No, there will be one write for each package on the command line, but not the libraries. If you upgrade it with emerge world, there will be no writes to world. Either way, it is a couple of seconds at most, out of several hours, when the file is actually being written. -- Neil Bothwick Why do kamikaze pilots wear helmets?
signature.asc
Description: PGP signature
