<html><head></head><body>Hi,<br><br>To the extent that we use Python to build VLC, and that it does not come with the OS, then we may need to provide Python for the build system. So that depends on the build OS really. But that has nothing to do whatsoever with this patch set, which does not introduce any build-time dependency on Python and does not cause Python to be shipped with VLC.<br><br>As for YoutubeDL, we don't use it to build VLC and we don't ship it in any form.<br><br>This is completely different from, say, OpenSSL, where you'd end up both needing the headers and import library to build, and where you'd ship byte code in whichever VLC module linked directly or indirectly with OpenSSL.<br><br><div class="gmail_quote">Le 21 septembre 2020 12:50:15 GMT+03:00, Steve Lhomme <robux4@ycbcr.xyz> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 2020-09-21 11:47, Rémi Denis-Courmont wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi,<br><br>Of course not. We don't package a compiler, a kernel, a display server <br>and a PulseAudio daemon. We don't package the decompressor binaries that <br>the decomp filter uses. We don't even package ALSA and GL libraries that <br>we have build-time dependencies on.<br><br>We need to provide sources for whatever we provide binaries. We don't <br>provide binaries of YoutubeDL nor Python 3.<br></blockquote><br>Doesn't it violate the GPL ? Python and all the things you cited can be <br>considered as part of the OS but youtube-dl I highly doubt it.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Le 21 septembre 2020 12:39:26 GMT+03:00, Steve Lhomme <robux4@ycbcr.xyz> <br>a écrit :<br><br> Virtual Environment<br> <a href="https://docs.python.org/3/tutorial/venv.html">https://docs.python.org/3/tutorial/venv.html</a><br><br> The other thing is that whatever VLC needs, it doesn't<br> pollute the<br> system environment, potentially introducing incompatible<br> dependencies.<br><br> Using a venv does not seem very useful here.<br> If packagers want to do that, thats a different story but<br> in general I dont think VLC should set up a venv because<br> it does not even install any dependency so it seems pointless<br> to do.<br> Even if we were to package it in contribs, a venv is probably<br> not needed as it seems youtube-dl has no dependencies itself<br> so it could just be easily imported without a venv.<br><br><br> I think we need to package it in VLC since we need to be able to make<br> package sources of whatever we use in VLC, our code, the contribs and<br> the tools.<hr> vlc-devel mailing list<br> To unsubscribe or modify your subscription options:<br> <a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a><br><br><br>-- <br>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser <br>ma brièveté.<hr>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a><br><br></blockquote><hr>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a></pre></blockquote></div><br>-- <br>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.</body></html>