Bug#881719: libcdio 2.1.0 and lubcdio++
Hi, Vasyl,
On 26 Jul 2020, Vasyl Gello wrote:
>I need it to satisfy kodi build dependency in libcdio++. Actually, when Kodi 19.0 goes live officially,
>I would like to have it in unstable, testing (if it gets released before the freeze takes place)
That sounds reasonable, and I'm already working on the upload to
unstable (I'll check that libcdio reverse dependencies [1] work
well with the new package, then make the upload).
[1] https://release.debian.org/transitions/html/auto-libcdio.html
>and at least,
>stable-bpo so end users have a chance to get backported, tested version without upgrading the whole installation.
Hmm, that's not a decision to be made lightly. Would the backport to
buster fix any bugs or add features that users have requested?
Maintaining a package in backports is more work.
>This will also greatly simplify add-on management as I have prepared the full binary addon repository for Kodi.
>Now stable has,17.6, unstable 18.7 and experimental will feature 19.0~.
Perhaps I do not understand the whole picture, but addons that work
with stable alone (i.e. stable without backports) have to be maintained
anyway (not every stable user enables backports). I don't see how
having an updated version in backports simplifies anything. It's
actually the other way around, as it adds more work for us.
>All addon sets are incompatible with each other and upstream backports only security and serious+ functionality
>bug fixes. Sticking to the latest release in all branches is a good move.
I don't think so, as it defeats the purpose of having a stable
distribution. And, in any case, people using the stable distribution
without backports enabled will keep using the older set of addons,
which might have security and serios functionality bugs, so we have to
take care of them anyway.
Let me know if I got anything wrong. :)
Cheers,
Gabriel
Reply to: