On Wed, 2005-03-30 at 20:16 +0100, Nicolai Guba wrote: > Nick Rout wrote: > > >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: > > > > > You might notice that sometimes it tries to unpack a package that is > currently being compiled if you emerge the same 'class'. > > Obviously that results in a 'pulled the chair under my arse' effect and > the compile fails because previously compiled objects are missing :P
Agreed, it pays to be careful, I would not do two complex ebuilds with many dependencies at the same time. And definitely check that both aren't going to emerge the same dependency. However, as an example, I was doing an install the other day, and emerged stuff lioke vixie-cron and mc at the same time. In fact at one point I was using 4 consoles with 2 or 3 emerges going and setting up rc files in the 4th. > > > -- > [email protected] mailing list > -- Nick Rout <[EMAIL PROTECTED]> -- [email protected] mailing list
