jose isaias cabrera wrote:
According to Jason, the one emerge does something ( waits? ) for the second emerge to complete, and then emerges the library twice. In this version of portage, this is the best that is going to happen until the internals are redone. I believe with new internals the emerge-twice deal will be taken care of, but don't quote me on that.
Is it safe to start another emerge while an emerge is running? I am
emerging openoffice and I started another session and emerged at. It
didn't complaint or anything, but now I am worry that some libraries may be
damaged by doing two emerges at the same time.
Any ideas?
If you are using 2.0.51 or later (which you should be :) then there should be
no harmful issues at all. The worst that should happen is that a package
might be emerged twice. If anything other than that occurs, please file a
bug.
My UltraSPARC portage profile got damaged when I upgraded to 2.0.51. :-) But, I am talking about another system that I have. :-)
Ok. Apparently, all is going well. But I would love to see someone doing two emerges of packages that share the same libraries. What would happen if one emerge is writing to a library while the other emerge is also trying to do the same? Hmmm....
Don't worry about it. I just asked to make sure that I didn't have to do the emerge at again or even worse, emerge openoffice. :-)
thanks.
-- [email protected] mailing list
-- Alec Warner Spartasoft Secretary ( spartasoft.msu.edu ) Junior Computer Science Michigan State University [EMAIL PROTECTED]
-- [email protected] mailing list
