On Monday 2018-09-24 15:52, Dominique Leuenberger / DimStar wrote:
Evince, a 'document viewer', has multiple backends. Traditionally, evince was used for displaying PDF and PS files (of which PS is even debatable).
I don't have a good recipe as to solve the underlying issue [of recommended, but not required, plugins] though: there is nothing the review could be asked to do
It is just a matter of "communication", IMO. The user needs to be aware that a certain program has a plugin architecture and extra packages may be needed. zypper already does mention to the user if there are recommended packages (Just noticed ... half of the time!? bug report - https://github.com/openSUSE/zypper/issues/206 ) Just mentioning plugins in the package description is my current idea. (Done for evince.)
as deciding about this must be done by maintainers that actually understand the package indepth, and hopefully also have some insight about the use of the package. Of course, may might ask upstream - but they will just recommend 'everything their app can do, as that's what they wrote it for'.
Not always possible; some plugins for some software may be provided by a second party. Also of note: LibreOffice does just that, and they do it at a build level: they link, rather than dlopen, all their format "plugins". (Which also means a larger minimal installation because you can't get rid of support for 1980s file formats.) Coming back to the "communication" part: Libraries... Many programs, when using libraries, do a rather bad job of conveying precise error messages that indicate a missing codec/plugin is the problem rather than a broken file. (Ironically, /usr/bin/ffmpeg, using the ffmpeg libs, itself was such a candidate. That received a patch in openSUSE to be more vocal on the command line about deactivated codecs.) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org