deadbeef-1.8.0[opus] or later: must be blocked by deadbeef-opus

[nick87720z]

There are file collisions when emerging deadbeef-1.8.0 due to deadbeef-opus.
My first think was to block deadbeef-soxr and/or deadbeef-meta-plugins[soxr] in deadbeef-1.8.0 or later ebuilds,
but another approach could be to block >=deadbeef-1.8.0 in deadbeef-soxr (or even >=deadbeef-1.0, just from my wild guess). Second approach seems simpler, because when deadbeef-soxr is deprecated (after removal of all <deadbeef-1.0), no cleanups are needed after package removal.

[damex]

this is the tricky one.

another possible way to solve - add a 'deadbeef player compatible version(s)' variable to plugin eclass to mark it as compatible with some deadbeef versions and block against others.

need to think about implementation though.
possibly correct way would be to add blockers for meta package use flags (same way as it has PDEPENDS) and somehow manage use as 'either USE from deadbeef or meta with USE flag' since we still can use externally built plugin with deadbeef instead of one that is internal/bundled with deadbeef.

[nick87720z]

Oh, I did not notice, that deadbeef has USE=opus, which could be used. Imho, adding blocker for deadbeef-plugins-meta[opus] is not enough, since plugins could be installed directly.

Btw, in this case adding to deadbeef ebuild: opus? (!! media-plugins/deadbeef-opus) could be simpler, since in other case (blocking deadbeef[opus] in deadbeef-opus) would require deadbeef-opus to be reemerged as well, only for block to take effect.