| 1 |
> --resume restarts an aborted or failed merge, but it starts it at the |
| 2 |
> _beginning_ of the last package being worked on. All compilation of |
| 3 |
> that package must be repeated. |
| 4 |
|
| 5 |
Is there a good reason a compile should resume in the middle? |
| 6 |
For what legitmate and safe reasons can you support this? |
| 7 |
|
| 8 |
I have explicitly rejected this many times because there are |
| 9 |
no realistic reasons to support potentially broken builds. If |
| 10 |
the compile fails, it probably isn't a singularity within that |
| 11 |
one file upon which it failed. |
| 12 |
|
| 13 |
Developers, of whom there is the knowledge of 'ebuild', can work |
| 14 |
around the restarting from the beginning issue. |
| 15 |
|
| 16 |
--NJ |
Archives