Re: [paludis-user] Rebuilding everything with cave --resume-file is awfully slow

[Rodolphe Rocca]

On 01/01/2011 01:50 AM, Ciaran McCreesh wrote:

On Fri, 31 Dec 2010 12:51:57 +0100
Rodolphe Roccamaitrech...@gmail.com  wrote:

Off course every user would appreciate things to go a little bit
faster if possible here :-)

The next major release includes a workaround for some libstdc++
stupidity that tends to make it try to write() one byte at a time.
That'll make a fair difference there...


paludis-0.58 is much faster indeed :-)

Thank you for this work !
___
paludis-user mailing list
paludis-user@lists.pioto.org
http://lists.pioto.org/mailman/listinfo/paludis-user

Re: [paludis-user] Rebuilding everything with cave --resume-file is awfully slow

[Ciaran McCreesh]

On Wed, 29 Dec 2010 12:41:20 +0100
Rodolphe Rocca maitrech...@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 ?

Yes.

 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 ?

No.

 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.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature
___
paludis-user mailing list
paludis-user@lists.pioto.org
http://lists.pioto.org/mailman/listinfo/paludis-user