VERY undesirable change in portage behavior :(

[curmudgeon]

I maintain an extensive list of ebuilds in /usr/local/portage.

After editing one, I run the command "ebuild foo-1.2.3.ebuild digest" to generate the Manifest and digest for the ebuild.

This USED to work fine (without any problems), but now (after a recent portage upgrade), this command generates a rebuild of the digests for ALL versions of foo.

In particular, this will start downloading the source for all versions of foo. Much of the time I have already moved the source to other machines (where I might need the ebuild), or possibly even deleted it (wanting to keep an old ebuild as a record or template of the modifications I have made). I absolutely NEVER want to download source code to this machine again (I always have the required files to satisfy the requirements for the ebuild for the version given in the ebuild command).

If I issue a command that says I want a digest for a particular version of foo, it means that I want a digest for that version of foo - not one for EVERY version of foo.

I hope someone knows a workaround for this. I absolutely can not tolerate this behavior, and will downgrade portage to the last version without this "feature" if I can't find a way of restricting the ebuild command to the version given.

[Genone]

This is due to a change in the checksum system as we now require SHA1 instead of MD5. There is no workaround for that (actually that it worked between 2.1 and 2.1.2-r9 was a bug that got fixed recently)

[curmudgeon]

[Genone]

[curmudgeon]