Mike Frysinger ha scritto:
On Thursday 24 March 2005 09:16 am, Francesco Riosa wrote:ah ok, I was confused by the fact that I can change patches and ebuild in my *overlays* without the need of a "ebuild P digest"
Chris Gianelloni ha scritto:
On Thu, 2005-03-24 at 14:22 +0100, Francesco Riosa wrote:ok, this is true only when you have FEATURES="strict" or "cvs" that it's
In addition to "Manifest" files in portage tree there are 19000Not if you ever want to ensure that what you're downloading hasn't been
"digest-${P}" files in the portage tree each of this uses 4k on ext{2,3}
filesystem and has to be scanned each time rsync is run on the tree.
Is possible to avoid the use of theese files?
trojaned or otherwise tampered with.
not the default.
no it's not
Manifest is checked when you have FEATURES=strict, digest is checked everytime you fetch/unpack files ... all those little 'src_uri md5' lines is a check against the digest
-mike
already found "digestCheckFiles" & "digestcheck" in portage.py so pointers not needed anymore.
thanks -- [email protected] mailing list
