Using opi yt-dlp, I eventually get to choose between installation from packman or network:utilities. The package version on OBS seems to be newer, but I’ve read somewhere that codec packages from packman where more fully featured as opposed to those from OBS, so that packman would be worth it despite lagging behind sometimes.
Is that also right for the dependencies of yt-dlp (ffmpeg etc.), or does it not matter in this case?
@suop Hi, you need to understand the nature of the Packman Build Service these days, many packages are links to packages on the openSUSE Build service and essentially Packman just rebuilds with certain items enable that are disabled on OBS…
To this end, N:U is the ‘development’ project for yt-dlp openSUSE Factory, updates get submitted to Factory, once accepted into Factory, the Packman version is just a build link, so then rebuilds with flags enabled once the new package appears.
As this process does have delays, the resulting packman version can take some time to appear.
Since there is only a ‘Requires’ on ffmpeg, I see no reason you can’t use the N:U repo in the short term. I suspect the reason for the link is just to centralize this package to the packman repo since it does use ffmpeg.
OK, thank you for explaining. It would be really neat then if there was an easy way to tell for each package what exactly is enabled in Packman that has to be disabled in OBS. The blacklist lacks details.
Anyway, I’ll first try N:U. I need ffmpeg to mux H.264/AVC content, when that doesn’t work out, Packman it is.
@suop aside from a few outliers, the bulk built by the third party provider Packman have some restriction on patents, licensing etc that cannot be enabled or built on OBS, hence built there…
In the end, I went with a mixed approach: Installing ffmpeg from packman (interactively using opi, or when the packman repo is already activated, with zypper in ffmpeg>=4), and yt-dlp from N:U.
This way, I got the newest version of yt-dlp and a fully functional ffmpeg, and since yt-dlp uses only the CLI interface of ffmpeg AFAIK, there is no trouble with this mix.