[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1040520: libheif1: Please don't split plugins in separate packages



Hi,

The reason for not depending on the plugin packages was that some
plugins provide support for the same codec but using different
libraries. So for example if users want to use rav1e for AV1 encoding,
they should not need to install the aomenc plugin. Or maybe I'm
thinking too technical and people don't really care about what is
installed...

I'm considering changing the packages that were provided as builtin
codecs in the past as "Depends" to libheif1. This will affect the
packages currently marked as "Recommends". Would that be acceptable?

Please note that together with the actual libheif plugin packages,
additional packages will be pulled in as dependencies.

Cheers,
  Joachim


On 07.07.23 16:29, marillat wrote:
On Fri, 07 Jul 2023 09:46:39 +0200 Christian Marillat <marillat@debian.org> wrote:
Package: libheif1
Version: 1.16.2-1+b1
Severity: serious

Dear Maintainer,

For people like me with Install-Recommends set to false,
no plugins are installed and I spend some time to understand why
program like didikam, thunar or imagemagick was unable to display any
.heic image files.

If you don't want to move back plugins packages to libheif1.

Here is and idea.

1) You must improve the long description for plugin packages.
    I read for libheif-plugin-libde265 "This package contains the
    libde265 plugin" (same for other packages).
    What is supposed to do this plugin (and others) ?

2) libheif1 must Depends on plugins that are able to open video and
  image files so that nothing is broken in others packages (imagemagick,
  thunar, etc)

Christian


Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: