Comment 22 for bug 1632870

Currently, i.e. as long as version 23+ of the NPAPI plugin is only beta and not officially released by Adobe, we are in limbo. However, Adobe can be expected to release the updated NPAPI soon, and when that happens, all this ought to be significantly easier to deal with. Hence I don't think it's worth too much effort to resolve the issues for this transitional period only.

In Ubuntu the only package needed should be adobe-flashplugin, which will provide updated versions of both NPAPI and PPAPI. pepperflashplugin-nonfree will be redundant, and so will, if I understand it correctly, the browser-plugin-freshplayer-pepperflash package (the "wrapper"). No need to make Firefox use the PPAPI plugin via a wrapper when there is an updated NPAPI.

It should be easier to handle from a Debian POV as well. Possibly - for license reasons - they can't mirror the adobe-flashplugin approach. Debian may need to keep pepperflashplugin-nonfree to download the PPAPI plugin (from Adobe), and they may need to have some other package download the NPAPI plugin. However, the wrapper shouldn't be needed in Debian either going forward.

As regards dependencies in Ubuntu, I don't think it's possible to let a package in universe/multiverse recommend or depend on a package in Canonical Partner, since the latter is not enabled by default.

I wish I could see a way to provide the users a smooth transition from pepperflashplugin-nonfree/browser-plugin-freshplayer-pepperflash to adobe-flashplugin, but I can't.

@Chris: I took the liberty to subscribe you to this bug report, since you maintain adobe-flashplugin.