| 1 |
On Friday 10 Feb 2017 19:39:44 Dale wrote: |
| 2 |
|
| 3 |
> I generally let emerge build packages in parallel. This works because a |
| 4 |
> lot of packages are small and don't take long to build or much room |
| 5 |
> either. However, there are a few exceptions. For me, Seamonkey, |
| 6 |
> Firefox and Libreoffice cause issues. I would like those to build one |
| 7 |
> at a time instead of at the same time. I've had times where all three |
| 8 |
> have updates but having two of them at the same time occurs pretty |
| 9 |
> regular. I thought I recalled this needing to be in package.env but my |
| 10 |
> test didn't work. I put this in package.env: |
| 11 |
> |
| 12 |
> www-client/seamonkey MAKEOPTS="-j1" |
| 13 |
> www-client/firefox MAKEOPTS="-j1" |
| 14 |
> |
| 15 |
> Since I'm here, you can guess that emerge didn't like that. So, either |
| 16 |
> I'm putting that in the wrong place, the wrong way or something. Oh, I |
| 17 |
> looked at the wiki and I didn't see things like this. I just went with |
| 18 |
> what little I recalled which seems to be not correct. |
| 19 |
|
| 20 |
The way you've set it will tell portage that, when it comes to emerging |
| 21 |
seamonkey, it should only use one process(or), and likewise for firefox. I |
| 22 |
think those options will only take effect within each package, not while |
| 23 |
deciding which packages to build. |
| 24 |
|
| 25 |
What you want is some kind of interlock, so that only one of the competing |
| 26 |
packages can be emerged at a time. I don't know how to do that, sorry. |
| 27 |
|
| 28 |
> ... I may want to disable portage on tmpfs as well, for Libreoffice at |
| 29 |
> least. |
| 30 |
|
| 31 |
I've seen a description of exactly that somewhere; you need two portage tmp |
| 32 |
directories, one tmpfs and one real disk, then switch from one to the other |
| 33 |
by redefining PORTAGE_TMPDIR in package.env. Something like that, anyway. |
| 34 |
|
| 35 |
-- |
| 36 |
Regards |
| 37 |
Peter |
Archives