Nick Rout wrote:
You might notice that sometimes it tries to unpack a package that is currently being compiled if you emerge the same 'class'.Not usually, but you might run into problems, if for example a library changes via one ebuild while another is compiling against it. perhaps.
I do it all the time, no probles so far.
I am not sure what will happen if the same package is in both lists, ie if emerge X has Y as a dependency, and emerge Z has the same dependency.
On Mon, 2005-03-28 at 17:22 -0800, Grant wrote:
Obviously that results in a 'pulled the chair under my arse' effect and the compile fails because previously compiled objects are missing :P
-- [email protected] mailing list
