>>>>> On Fri, 20 Dec 2019, Michael Orlitzky wrote:

> Portage seems OK with the missing dependency, but for the overall plan
> to work, you have to wait a long time before deleting virtual/emacs;
> otherwise the upgrade path is broken. With virtual/emacs-26 installed
> and "old" copies of the elisp ebuilds installed, you get unsatisfied
> dependencies switching from emacs-vcs to a live slot of emacs. Everyone
> in that situation must update to virtual/emacs-26-r1, which they can't
> do after you delete it.

> And of course you can't mask virtual/emacs in the meantime, because that
> does kill the PM.

I have no plans of masking the virtual. It will be simply removed,
presumably after the app-editors/emacs-27.1 release (at which point any
emacs-vcs-27.0* will be outdated, and be blocked against by the ebuild).

> New revisions would still be the sane solution, now and in the future,
> because they don't require investigative journalism to uncover exactly
> what might go wrong when we bend the rules /this time/. They also don't
> impose a cutoff date after which upgrading users are screwed. You just
> automate the revbumps, commit them all at once, and make a pull request
> against CI to verify that nothing is too borked.

See? You say it yourself, with 400 revbumps there is quite some chance
for breakage.

Ulrich