After this change:
When migrating from pulseaudio following the instructions from the news item:
People will end-up without any alsa-plugins by default just after doing the depclean as suggested by the news item. This is because, at the time of the migration, media-plugins/alsa-plugins[pulseaudio] will be present at the time the elog message should be shown as it's still there pulled in by the pulseaudio. As a consequence, optfeature.eclass won't show the warning.
I noticed it just now when migrating one of my machines, as I was surprised of seen alsa-plugins in the (long) list of packages I needed to clean. I am not sure what option would be better:
- Enabling pipewire-alsa by default -> It looks the simplest and more future-proof, but it seems to not be enabled due to some runtime checks it should do (as I read from comments in the ebuild)
- Update the news item to remind people that they should ensure alsa-plugins[pulseaudio] is still there after depcleaning when pipewire-alsa is not enabled.
Confirmed, it bited me.
Other option could be to have something as FORCE_PRINT_ELOG from readme.gentoo.eclass in optfeature.eclass to, later, force the printing when updating (and needed) via has_version checks