| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Brian Harring wrote: |
| 5 |
> I might be daft (likely), but why not just introduce a var indicating |
| 6 |
> max parallelization instead? Tweak portage to push that setting into |
| 7 |
> MAKEOPTS="${MAKEOPTS+${MAKEOPTS} } -j${PARALLELIZATION}". |
| 8 |
|
| 9 |
The idea sounds good, but I'm not clear on all the details. It |
| 10 |
seems like there are several distinct parts: |
| 11 |
|
| 12 |
1) Ebuild maintainter sets a metadata variable to indicate the level |
| 13 |
of parallelization possible in a build. |
| 14 |
|
| 15 |
2) Gentoo user sets a configuration option indicating the maximum |
| 16 |
level of parallelization spread across multiple builds at a given time. |
| 17 |
|
| 18 |
3) Package manager uses the user's config to allocate an appropriate |
| 19 |
PARALLELIZATION at build time, based on 1 and 2 above. Then the |
| 20 |
src_compile() function of the ebuild translates PARALLELIZATION into |
| 21 |
the appropriate build system flags (possibly with the help of an |
| 22 |
eclass function). |
| 23 |
|
| 24 |
Is that about right? |
| 25 |
|
| 26 |
Zac |
| 27 |
|
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.4.5 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFFK3QE/ejvha5XGaMRAnBGAJ9sbEd148y1bM8egAH7WtTQDl5yuwCeLMjf |
| 32 |
2M8OA0mIY1jw0NVTkzMuudk= |
| 33 |
=qaHg |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-portage-dev@g.o mailing list |
Archives