ke 6. marrask. 2024 klo 13.50 Fabian Greffrath (fab...@greffrath.com) kirjoitti: > > Am 2024-11-06 10:53, schrieb Martin-Éric Racine: > > ffmpeg aleady ships generic libav*-extra packages that depend on the > > latest versions. It would be desirable to also ship non-extra versions > > of these. > > Could you elaborate your use case, please? The non-extra variants of the > shared library packages are installed by default, i.e. they are first > choice in the list of alternative dependencies that shlibdeps creates. > The -extra dummy packages are there to make sure that the extra variants > of the libraries are preferred. So, what would be the use case of a > non-extra package?
One example is the non-free Spotify client. Its dependencies currently are as follow: Depends: libc6 (>= 2.30), libasound2, libatk-bridge2.0-0, libatomic1, libgbm1, libglib2.0-0, libgtk-3-0, libnss3, libxshmfence1, libxss1, libxtst6, xdg-utils, libayatana-appindicator3-1 Recommends: libavcodec58 | libavcodec-extra58 | libavcodec57 | libavcodec-extra57 | libavcodec-ffmpeg56 | libavcodec-ffmpeg-extra56 | libavcodec54 | libavcodec-extra-54, libavformat58 | libavformat57 | libavformat-ffmpeg56 | libavformat54 That long Recommends would make more sense if it were: Recommends: libavcodec | libavcodec-extra, libavformat | libavformat-extra Replacing all the *-extra with the metapackage already is possible. Replacing the non-extra ones is not. Martin-Éric
