[libav-bugs] [Bug 224] Please export url.h and ffurl_register_protocol() function

bugzilla-daemon at aruru.libav.org bugzilla-daemon at aruru.libav.org
Wed Feb 8 21:36:00 CET 2012


--- Comment #9 from Ilya Murav'jov <muravev at yandex.ru> 2012-02-08 21:36:00 CET ---
> [...]
> That explains why we don't like that use. Now, second, as for the public API
> deprecation: we don't like the implementation. At all. It's horrible and ugly,
> and we can't fix it or even add new struct members, because it's public. So we
> decided to remove the public API so we can completely overhaul and redo it
> while it's private, and then _maybe_ export it again after that if there's a
> legitimate use case for it. Best example is how you could use a URLContext as a
> av_log() context because we couldn't add a AVClass to the beginning of it
> because it'd break ABI...

ABI breaking is not a problem for me. I would like libav be a library, not a
framework that tell me what I do and how to do it. If I want a framework I'd
choose GStreamer but I don't want it.

You deprecated URLContext - ok, but don't close the code you use yourself in
libav. I just want to be a first class citizen using the library. Change/fix it
- I don't mind but let me use it.

And I don't mind if there is DVD code in libav. 2 problems about rewriting my
code in libav: 1) I am not a DVD expert (yeah, I don't have those DVD specs for
$5000) and it was 2 years ago when I wrote it 2) I don't have time to a)
rewrite subj and b) rewrite it in libav C way (including
http://libav.org/developer.html) which I don't know.

Configure bugmail: https://bugzilla.libav.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the libav-bugs mailing list