| 1 |
Brian Harring wrote: |
| 2 |
> Note that due to how it's implemented, this does two rounds of |
| 3 |
> verification- it'll actually do *two* rounds of fetching too, if |
| 4 |
> things go awry in the backgrounded thread. |
| 5 |
|
| 6 |
Two possible improvements to help prevent user confusion: |
| 7 |
|
| 8 |
1) Display a warning message when waiting for distlocks and parallel-fetching is enabled, in order to alert the user that background fetching is likely in progress. |
| 9 |
|
| 10 |
2) Display a warning message via an atexit hook when parallel-fetching is enabled, in order to alert the user that background fetching may _still_ be in progress if emerge appears to hang after an ebuild dies (this happened to me while kde-3.5 was fetching in the background). |
| 11 |
|
| 12 |
Zac |
| 13 |
-- |
| 14 |
gentoo-portage-dev@g.o mailing list |
Archives