![]() ![]() I've been building mpv live since I first installed it years ago and this feels like a significant downgrade to me. Not to pile-on or be overly negative, but looking over this situation in sum, the retrograde commentary on how this forking silliness won't possibly affect downstream for several years because **Debian**, and their unwillingness to comprehend how this punishes distros and users that actually **do** compile from their repo (the defense being, essentially, "well, downstream doesn't care about us, so we won't care about it!"), I gave up and simply transitioned to their most recent release in the tree. ![]() However I'll put all the necessary machinery in the ebuild so it should build once ffmpeg devs review and merge those patches. Ĭurrently one cannot build mpv-9999 with ffmpeg-9999, because some of the patches submitted by mpv devs weren't merged, which is the whole reason of this fork. Using a ffmpeg fork (which will always be just small patches ontop of upstream ffmpeg) will be so much easier.Īlso "just let wm4 have his ragefork for a week or two". I'm not interested in waiting weeks until I can get certain patches into ffmpeg, and then wait a few months until the next ffmpeg release, and a few years until distros like debian finally support it. Having to worry about this is quite grating, especially when I added the API myself. So I don't have to worry anymore about "when" I can use a certain new FFmpeg API. The real reason I'm doing is so I can control what FFmpeg is used exactly and therefore what set of APIs is available to me (as a developer) exactly. Its only purpose is to please certain mpv devs : ![]() It's going to be in unstable limbo and probably won't have any releases ever. Thank you for patches and stuff, but I don't recognize any usefulness in bringing ffmpeg-mpv in Gentoo. Turns out the problem with the runtime being different on running mpv -V was due to me not updating my tomoyo policies. ![]() > Also I get that I am using a different runtime version of labavcodec when I > ffmpeg-mpv) with FFTOOLS set to -*, there are package collisions. > ffmpeg packages fail to link), and if I don't build one of these (ffmpeg or > I have to build with ffmpeg git installed or mpv fails to link (non -9999 (In reply to stressfactor from comment #10) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |