1 |
Dnia 2015-01-17, o godz. 20:48:11 |
2 |
Zac Medico <zmedico@g.o> napisał(a): |
3 |
|
4 |
> On 01/17/2015 08:22 PM, Zac Medico wrote: |
5 |
> > On 01/17/2015 02:45 AM, Michał Górny wrote: |
6 |
> >> Default MAKEOPTS job number to (number of CPUs + 1) when it is not |
7 |
> >> provided in the ebuild environment. |
8 |
> >> |
9 |
> >> Suggested-By: Daniel Robbins <drobbins@××××××.org> |
10 |
> >> --- |
11 |
> >> pym/portage/package/ebuild/doebuild.py | 8 +++++++- |
12 |
> >> pym/portage/util/cpuinfo.py | 19 +++++++++++++++++++ |
13 |
> >> 2 files changed, 26 insertions(+), 1 deletion(-) |
14 |
> >> create mode 100644 pym/portage/util/cpuinfo.py |
15 |
> > |
16 |
> > LGTM. |
17 |
> > |
18 |
> |
19 |
> Actually, Arfrever tells me that the multiprocessing module is not |
20 |
> available if python is built without threading support. So, we need to |
21 |
> handle the ImportError and either do nothing or parse /proc/cpuinfo or |
22 |
> something like that. |
23 |
|
24 |
I don't think there's a point in having more complexity for a use case |
25 |
that doesn't really get used. Except maybe for the few 'USE=-*' people |
26 |
who aren't cautious enough but they're going to be hit by some failure |
27 |
sooner or later. |
28 |
|
29 |
I'm going to remove the flag on the Python end after verifying |
30 |
the USE-deps. |
31 |
|
32 |
-- |
33 |
Best regards, |
34 |
Michał Górny |