<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 17.06.24 um 22:58 schrieb Howard
Chu:<br>
</div>
<blockquote type="cite"
cite="mid:56e242bd-e8fa-694a-7aae-8e0dad0abe26@highlandsun.com"><span
style="white-space: pre-wrap">
</span>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Will there be an official release 2.6 (preferably in the form of a tarball)?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Maybe. We haven't done tarballs in quite a long time. A git tag would be more likely.</pre>
</blockquote>
<p>As far as vcpkg is concerned: it will use asset caching for
tarballs, but not for git.</p>
<p>(librtmp won't be used in every build, but calling git isn't the
preferred form to get official sources.<span
style="white-space: pre-wrap">)
</span></p>
<blockquote type="cite"
cite="mid:56e242bd-e8fa-694a-7aae-8e0dad0abe26@highlandsun.com">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">What is the recommendation on the proliferation of usage of librtmp/rtmpdump:
- accept new downstream references (such as adding an rtmp feature to the curl port in vcpkg),
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
curl support of librtmp has been around for many years already.</pre>
</blockquote>
I'm aware of that. This capability is the driver for (others)
touching vcpkg port librtmp now and possibly making the capability
available now. I wonder if it is worth the ongoing maintenance
burden in vcpkg - in particular if it isn't actually used or tested
by the contributors who touch these ports now.<span
style="white-space: pre-wrap">
</span>
<blockquote type="cite"
cite="mid:56e242bd-e8fa-694a-7aae-8e0dad0abe26@highlandsun.com">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">- freeze the current status, or
- actively delist it from registries (like vcpkg)?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
The statement "nobody should be using this any more" is about RTMP itself.
Adobe officially killed Flash, as of December 31, 2020.
<a class="moz-txt-link-freetext" href="https://www.howtogeek.com/700229/adobe-flash-is-deadheres-what-that-means/">https://www.howtogeek.com/700229/adobe-flash-is-deadheres-what-that-means/</a>
Flash was the only official client for RTMP. With that gone, there's no reason for anybody to
be using an RTMP server any more, and thus no reason for anyone to be using librtmp in any
clients any more.
</pre>
</blockquote>
<p>Thanks.<br>
Kai Pastor<br>
</p>
<br>
</body>
</html>