| 1 |
* Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> If one instance of emerge doesn't know what the other instance has |
| 3 |
> already done, then the second one could emerge it again. Doesn't emerge |
| 4 |
> do all the calculating at the beginning and runs with that until the end? |
| 5 |
|
| 6 |
That's also one of my questions - does parallel emerge instances |
| 7 |
know if some dependency had already been built/installed in the middle ? |
| 8 |
|
| 9 |
> I am using the -j option for the first time now. I'm updating KDE. It |
| 10 |
> seems to work fine. It doesn't scroll all the stuff like with a regular |
| 11 |
> emerges but this new rig is so fast, I can't read it anyway. I did have |
| 12 |
> a package to fail and it spit out the error for me to read. |
| 13 |
|
| 14 |
BTW: does -j / --jobs also cause a parallel make (-j parameter to gmake) ? |
| 15 |
|
| 16 |
|
| 17 |
cu |
| 18 |
-- |
| 19 |
---------------------------------------------------------------------- |
| 20 |
Enrico Weigelt, metux IT service -- http://www.metux.de/ |
| 21 |
|
| 22 |
phone: +49 36207 519931 email: weigelt@×××××.de |
| 23 |
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 |
| 24 |
---------------------------------------------------------------------- |
| 25 |
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme |
| 26 |
---------------------------------------------------------------------- |
Archives