#531 add a resume feature to dunecontrol
Metadata
| Property | Value |
|---|---|
| Reported by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
| Reported at | Apr 7, 2009 06:34 |
| Type | Feature Request |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
| Last edited at | Jun 5, 2009 09:06 |
| Closed by | Martin Nolte (nolte@mathematik.uni-freiburg.de) |
| Closed at | Jun 5, 2009 09:06 |
| Closed in version | Unknown |
| Resolution | Implemented |
| Comment | skipfirst should is not reallly necessary. |
Description
Assume you have several projects in your dune directory. Now, if you run dunecontrol over all of these, it happens that one module or the other just does not work out of the box. This means that you have to rerun dunecontrol for all projects (or call it by hand for every project remaining).
In this scenario, a resume feature would be a great help. We could, for example, clone the resume semantics from the Gentoo emerge script and say
dunecontrol --resume resume the last run, completely rebuilding the module that failed
dunecontrol --resume --skipfirst resume the last run, skipping the module that failed