I ran into the verification error as well. Frankly I would prefer it not run a sync during the script but the portage tarballs apparently now lack some bits required to use portage (I haven’t used gentoo in a while so I could be off here) due to a missing db or something. If you know how to rebuild the db without doing a sync I would update to that.
In issue #3 we discussed verification issues on emerge --sync, this issue is about investigating how to handle portage and the database to avoid that sync since it extracts a portage tarball onto the filesystem and syncing is unnecessary if we can use what's already there.
My first inclination is to look at what emerge-websync or emerge --sync does and replicate the parts that deal with updating portage's internals after the download.
In issue #3 we discussed verification issues on emerge --sync, this issue is about investigating how to handle portage and the database to avoid that sync since it extracts a portage tarball onto the filesystem and syncing is unnecessary if we can use what's already there.
My first inclination is to look at what emerge-websync or emerge --sync does and replicate the parts that deal with updating portage's internals after the download.