| 1 |
Peter Volkov <pva@g.o> writes: |
| 2 |
|
| 3 |
> This variable will be used in eclasses so it's better to avoid portage |
| 4 |
> in it's name, since not only portage will work with it. GENTOO_JOBS is |
| 5 |
> really something new in sense of consistency. EJOBS looks most terse for |
| 6 |
> me but I'll be ok with any name... |
| 7 |
|
| 8 |
It's just I don't want to end up colliding with other stuff like |
| 9 |
EclipseJobs or something else. |
| 10 |
|
| 11 |
And my reason to not propose PORTAGE_JOBS is actually that it suggests |
| 12 |
relation with -j option to emerge rather than make ;) |
| 13 |
|
| 14 |
> For load average may be it's good to use another variable to avoid |
| 15 |
> overloading of "JOBS" meaning? |
| 16 |
|
| 17 |
Agreed, easier than ending up having to parse a variable content, after |
| 18 |
all environment variables are kinda cheap. |
| 19 |
|
| 20 |
-- |
| 21 |
Diego "Flameeyes" Pettenò |
| 22 |
http://blog.flameeyes.eu/ |
Archives