Bug 29333 – portage shouldnt check manifests/digests unless the ebuild operation is related to such

• Status: RESOLVED FIXED
• Product: Portage Development

[Description SpanKY 2003-09-22 07:21:11 UTC]

when compiling/installing/qmerging it's a waste of time to run through the md5sums
of all the files and such ... just another speed up ;)

[Comment 1 SpanKY 2003-09-22 07:22:45 UTC]

Created attachment 18126 [details, diff]
portage.py-digest.patch

[Comment 2 Nicholas Jones (RETIRED) 2003-12-24 12:46:09 UTC]

I don't follow what you're trying to do.

[Comment 3 SpanKY 2003-12-24 13:36:50 UTC]

if i do `ebuild <ebuild> clean unpack compile install` then the manifest/digest checks are run 3 times

it should *only* be run when unpack is run, otherwise it's a waste of resources ... and sometimes impossible to do (distfiles has gone  awol but i still got the WORKDIR in usuable shape)

[Comment 4 Marius Mauch (RETIRED) 2004-08-03 12:56:33 UTC]

*** Bug 25005 has been marked as a duplicate of this bug. ***

[Comment 5 SpanKY 2005-03-22 20:47:55 UTC]

Created attachment 54201 [details, diff]
no-digest-checks-all-the-time.patch

updated patch for HEAD ... this will only check the digests during the unpack
phase

[Comment 6 Jason Stubbs (RETIRED) 2005-07-14 05:47:49 UTC]

Fixed on or before 2.0.51.22-r1 

[Comment 7 Jason Stubbs (RETIRED) 2005-07-14 06:58:34 UTC]

Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.