Quantcast
Channel: Kodi Community Forum - All Forums
Viewing all articles
Browse latest Browse all 84011

dependency management in stable releases

$
0
0
Hi XBMC team,

Thank you for your excellent product. I enjoy using XBMC weekly.

I'm a co-maintainer for the RPM Fusion XBMC package, and recently I ran into a dependency issue when updating XBMC from 12.0 to 12.1 on Fedora.

Similar to Debian, Fedora's Packaging Guidelines prohibit bundled libraries (link), so we can't ship the libcec fork in the XBMC tree. Ordinarily this is not a problem; XBMC 12.0 worked with the libcec 2.0.5 package as shipped in Fedora 18. However, when XBMC 12.1 was released, it had a hard dependency on libcec 2.1. When we upgraded to 12.1 on Fedora 18, the package could no longer support libcec on that Fedora release.

A Fedora user has filed an RFE to ask the libcec maintainer to update his package in Fedora 18 (link), and it's possible that he'll be generous and agree to push the update.

However, I am also interested in respectfully letting you know about the situation. I was not expecting such a bump during a minor point release. On some levels, this certainly "comes with the territory" of trying to follow strict Packaging Guidelines on Linux distros, and I readily accept that dependencies have to be bumped from time to time. All the same, I think it's important for packagers and upstream devs to regularly communicate, and perhaps that communication can be more general, like this post. I'm posting this with the hope that you may take what I'm saying into consideration for future stable releases.

XBMC has come a long way towards unbundling several libraries, and I'd be amiss if I didn't say "thanks!" too for all that work.

- Ken

Viewing all articles
Browse latest Browse all 84011

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>