Re: [gentoo-dev] [PATCH 0/3] elisp{,-common}.eclass update for emacs-vcs consolidation

[Michael Orlitzky <mjo@gentoo.org>]

On 12/18/19 6:28 PM, Michael Orlitzky wrote:
> 
> This *does* happen if you mask virtual/emacs. It *could* happen if you
> delete it.
> 

I tested this out.

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.

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.