1 |
Dear devs, |
2 |
|
3 |
i've just hit the constraint CHECKREQS_MEMORY=3G in |
4 |
>=www-client/chromium-44.* on a 2 GiB RAM machine.. (having additionally |
5 |
5G Swap on SSD..) |
6 |
|
7 |
I personally doubt that check-reqs_memory() in the eclass should only |
8 |
check for *physical* rather than *virtual* RAM to fulfill this |
9 |
constraint and fail if unsatisfied. |
10 |
|
11 |
So my proposal would rather be: |
12 |
|
13 |
* $CHECKREQS_MEMORY<=pysical RAM -> ok |
14 |
* $CHECKREQS_MEMORY>pysical RAM && <= virtual RAM -> ewarn |
15 |
* $CHECKREQS_MEMORY>virtual RAM -> eerror (may still be overridden by |
16 |
${I_KNOW_WHAT_I_AM_DOING} in check-reqs_output() ) |
17 |
|
18 |
what do you think? |
19 |
|
20 |
cheers |
21 |
Christian |