FS#65277 - [gst-plugins-bad] build without libtiger/libkate so it won't depend on python2
Attached to Project:
Arch Linux
Opened by Jake Dane (jakedane) - Sunday, 26 January 2020, 11:47 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 26 January 2020, 15:16 GMT
Opened by Jake Dane (jakedane) - Sunday, 26 January 2020, 11:47 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 26 January 2020, 15:16 GMT
|
Details
Description:
With python2 being end of life I'm surprised gst-plugins-bad 1.16.2-2 added python2 as an implicit dependency. This stems from 1.16.2-2 moving libtiger from makedepends to depends. libtiger in turn depends on libkate which depends on python2. libtiger adds karaoke text (kate) support and is optional for gst-plugins-bad. I would suggest to build gst-plugins-bad without depending on libtiger and with kate disabled (build option '-D kate=disabled') so there won't be an implicit python2 dependency. libkate has had no upstream development in 8 years so migration to python3 is unlikely: https://git.xiph.org/?p=users/oggk/kate.git;a=summary Additional info: * package version: 1.16.2-2 Steps to reproduce: installing gst-plugins-bad 1.16.2-2 will also install python2 |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Sunday, 26 January 2020, 15:16 GMT
Reason for closing: Not a bug
Additional comments about closing: gst-plugins-bad doesn't depend on python2, removing features just because somewhere down the line a dependency tree invokes python2 is wrong.
You can open another bug against libkate itself to drop the python2 component, though. Because libkate depending on an end-of-life python2 is a maintainability issue regardless of whether you personally have software that requires libkate!
Sunday, 26 January 2020, 15:16 GMT
Reason for closing: Not a bug
Additional comments about closing: gst-plugins-bad doesn't depend on python2, removing features just because somewhere down the line a dependency tree invokes python2 is wrong.
You can open another bug against libkate itself to drop the python2 component, though. Because libkate depending on an end-of-life python2 is a maintainability issue regardless of whether you personally have software that requires libkate!