-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16.02.2012 14:09, Allan Gottlieb wrote: > On Thu, Feb 16 2012, Neil Bothwick wrote: > >> On Wed, 15 Feb 2012 21:31:02 -0500, Allan Gottlieb wrote: >> >>> That's it! I had collision-protect in make.conf. I just now >>> removed it and indeed emerge --info shows protect-owned. I >>> have an emerge of libreoffice running now. But hope tomorrow >>> to be able to retry the nvidia-drivers emerge and see if it >>> goes through. >> >> There's no reason why you can't do it while the LO emerge is >> still running. > > First, let me report success (I ran the emerge of nvidia-drivers > after LO finished and it worked fine) and thanks. > > I didn't realize that I could run emerges together. The emerge of > LO was the penultimate merge coming from an emerge update world > (the last was LO-l10n) While this LO merge was in progress could I > have safely started another emerge update world ? > > I am guessing the point is that, since the running emerge was > essentially just LO, it was safe to run the nvidia-drivers emerge > since there are no shared dependencies. Is emerge by some chance > clever enough that you can always start an update world, while one > is running? > > thanks again, allan > > Two "emerge update world"s I wouldn't recommend, because most likely you would emerge some packages two times. emerge <package> while "emerge --update world" is running is reasonably stable, at least in my experience. The biggest problem is slowdown and maybe out-of-memory-errors if you emerge multiple big packages (e.g. libre office and chromium).
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPPQL4AAoJEJwwOFaNFkYcEkkIAKPS7VgHjeFC6eG700aMOu/7 PHvgkKpsyeEZO78V65zFJePMyNBSzbskY5uXCtz2MLLHsuSkyznvJxzXNy/kycL8 6vFAHx6yKgQeudTaXkYxh9FhhVRSbnkedBqVR1x2k+1yhHTjQdsG5iDq0yBZucYi Hij1KIPKuylhAegp6v0c37dHbB9y9dmKAIW8wYxGfU2sOj6om2ALFZgKWfS1UpQx 1oWjWW93SV68qGVEGXDAyW1DvfDAhfYXF4b6WkCfBBZGVAyRtfRbSIQCs5R6piJi lr97+765+FFOXc/4DxtNPL4bLg40iEynJRQUJrQV2ukibAFusACfskB9MFpg4WY= =Bw/t -----END PGP SIGNATURE-----
