On Mon, Mar 26, 2018 at 10:16:06PM +0700, nablet developer wrote: > On 26-Mar-18 22:14, Diego Biurrun wrote: > > On Mon, Mar 26, 2018 at 11:37:49AM -0400, Sven Dueking wrote: > > > --- a/configure > > > +++ b/configure > > > @@ -4710,6 +4714,7 @@ enabled omx && require_header > > > OMX_Core.h > > > +enabled opensrt && require_pkg_config libsrt "srt >= 1.2.0" > > > srt/srt.h srt_socket > > Why do you call this thing opensrt when it calls itself libsrt? > > > names srt and libsrt were found confusing and misleading, because of > similar acronyms used for other multimedia related things which are > pretty well-known and wide-spread already (e.g. SRT subtitles or SRTP > protocol). as result, maintainers/reviewers asked to change name to > avoid confusion, and Haivision recommended to use "opensrt" naming in > order to distinguish from other similar acronyms.
The problem is that Haivision does not use "opensrt" as name, they use "SRT/srt" and libsrt. Using a different name inside libav does not really help in reducing that potential for confusion. If Haivision recommends "opensrt", why don't they change the name of their library? Better yet, why don't they change the name of the protocol? Notice that what I gathered from the discussion was people complaining about the bad naming choice, not suggesting "opensrt" as the alternative. I have asked this before: what is your relationship to Haivision? Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
