On Fri, Jul 6, 2018 at 3:02 PM Grant Edwards <grant.b.edwa...@gmail.com> wrote: > > Now that the public key stuff is working again (knock on wood), I'm > curious if it's usual for an emerge --sync to take 10-15 minutes > longer than it used due to the "Verifying /usr/portage" step. >
Again, the sync mechanisms are different, but I note that the git verify is nearly instant. Of course, the only thing being fed to gpg in the git case is the git commit record itself, which is about 10 lines of text. That record contains a content hash of the tree record, which in turn references content hashes of every directory inside, and so on. So, with git most of the hash validation is happening constantly just by virtue of everything being content-hashed, and the only extra layer with the gpg signature is to sign the top level of the whole tree. Now, on the flip side, some of those git operations might take time since it is stating files for things like git status/etc. I've never noticed an issue, but I'm also on an SSD and tend to always have a warm cache when I'm using it. emerge shouldn't need to trigger any git operations except when syncing. -- Rich -- Rich
