[paludis-user] Rebuilding everything with cave --resume-file is awfully slow
ciaran.mccreesh at googlemail.com
Fri Dec 31 07:59:50 UTC 2010
On Wed, 29 Dec 2010 12:41:20 +0100
Rodolphe Rocca <maitrechang at gmail.com> wrote:
> Each time an archive integrity is checked, the resume file is written.
No, it's written after a successful fetch.
> Is everything written to the resume file really meaningful
> resume information ?
> The paludis client is many times faster here.
The Paludis client doesn't store continue-on-failure information in
there, which means it gets things wrong later on.
> Moreover If I CTRL-C, the resume file gets corrupted.
> Isn't there a signal handler catching this signal and waiting for the
> resume-file being completely written before exiting gracefully ?
> NB: The reason why I want to do a CTRL-C here is that the
> installation is stuck at etqw-data waiting for my action to input a
> data dvd, but it fails to find it. So I want to modify the resume
> file by hand to remove etqw-data. Do you see any better way to handle
> this kind of situation ?
You can't edit resume files.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: not available
More information about the paludis-user