| 1 |
On Wed, Nov 30, 2005 at 12:51:58PM -0800, Zac Medico wrote: |
| 2 |
> Brian Harring wrote: |
| 3 |
> >Note that due to how it's implemented, this does two rounds of |
| 4 |
> >verification- it'll actually do *two* rounds of fetching too, if |
| 5 |
> >things go awry in the backgrounded thread. |
| 6 |
> |
| 7 |
> Two possible improvements to help prevent user confusion: |
| 8 |
> |
| 9 |
> 1) Display a warning message when waiting for distlocks and |
| 10 |
> parallel-fetching is enabled, in order to alert the user that background |
| 11 |
> fetching is likely in progress. |
| 12 |
portage_locks does so already. |
| 13 |
|
| 14 |
> 2) Display a warning message via an atexit hook when parallel-fetching is |
| 15 |
> enabled, in order to alert the user that background fetching may _still_ be |
| 16 |
> in progress if emerge appears to hang after an ebuild dies (this happened |
| 17 |
> to me while kde-3.5 was fetching in the background). |
| 18 |
Details please... |
| 19 |
atexit portage_exec hooks should kill off the fetcher. |
| 20 |
~harring |
Archives