On Fri, Feb 8, 2019 at 10:18 PM Jean-Baptiste Kempf <j...@videolan.org> wrote: > > On Fri, 8 Feb 2019, at 22:08, Lou Logan wrote: > > On Fri, Feb 8, 2019, at 11:27 AM, Jean-Baptiste Kempf wrote: > > > > > > Also, the AUR recipe does not push for non-free packages. > > > > The proposed homebrew formulae will not push for non-free packages. It > > will simply provide the options for the user to enable two non-free > > components (openssh and fdk-aac currently) if they desire. They have to > > be explicitly enabled by the user by manually including the appropriate > > option, such as "--with-fdk-aac". > > Yes, and this is exactly what I am objecting against. > It silently enables non-free, when you ask either. See L 146 and following.
You could print an even more obvious warning message when these options are used. If that is a big concern, it can be easily dealt with. > And yes, I strongly advise against the project advertising those non-free > options. Then the only consequence can be to remove these options or support for these libraries altogether, because you'll find plenty of guides and recommendations on how to build ffmpeg with non-free libs on the Internet – even supplied by members who are very active in the FFmpeg community. It is certainly your prerogative to be against explicit advertising, but where do you draw the line? Has there been any precedent with this, or is this going to be decided on a case-by-case basis? The only consequence would be a formula that is not owned and controlled by FFmpeg, and people will continue to build non-free binaries. Werner _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel