From owner-freebsd-ports@freebsd.org Wed Mar 8 20:34:49 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45696D03462 for ; Wed, 8 Mar 2017 20:34:49 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22D3A1EBA for ; Wed, 8 Mar 2017 20:34:49 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 6AD407E3D; Wed, 8 Mar 2017 20:34:48 +0000 (UTC) To: freebsd-ports@freebsd.org Subject: Re: Best way to cause synth to ignore rebuilding of a port?? In-Reply-To: Message-Id: <20170308203448.6AD407E3D@freefall.freebsd.org> Date: Wed, 8 Mar 2017 20:34:48 +0000 (UTC) From: jbeich@freebsd.org (Jan Beich) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2017 20:34:49 -0000 Kevin Oberman writes: > On Wed, Mar 8, 2017 at 8:40 AM, Lars Engels wrote: > >> On Wed, Mar 08, 2017 at 04:34:45PM +0000, Matthew Seaman wrote: >> > On 2017/03/08 16:04, Bob Willcox wrote: >> > > Note that I haven't tried ver 52 of firefox, but from what I've read >> it sounds >> > > like all plugins/addons other than flash are no longer supported. >> > >> > Make that: all *NPAPI* plugins other than Flash are now unsupported. >> > That's stuff like the Java plugin or the OpenH264 Video Codec from Cisco >> > (which I seem to have installed and can no-longer remember why. Some >> > sort of video conference thing a long time ago). >> >> The OpenH264 plugin is shipped out of the box. Only on Tier1 platforms (Windows, OS X, Android, Linux) where Firefox downloads it[1] shortly after install. The situation is similar with Widevine CDM or soon PPAPI Flash[2]. Even if someone provided FreeBSD binaries or implemented a wrapper[3] it'd also lower security due to lack of sandboxing[4]. WebAssembly should obsolete native code but existing plugins are unlikely to go away in near future. [1] Downstream builds lack patent license, see http://www.openh264.org/BINARY_LICENSE.txt [2] http://searchfox.org/mozilla-central/source/browser/extensions/mortar/host/flash/bootstrap.js [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1295853#c13 [4] https://wiki.mozilla.org/Security/Sandbox > And is required for HTML5 video if it is X.264 encoded, as it most often is. OpenH264 only supports Baseline profile and primarily used for WebRTC. For HTML5 videos Firefox uses FFmpeg (H.264, VP9), libvpx (VP8), libtheora. $ x264 -o bar.mp4 foo.y4m [...] x264 [info]: profile High, level 3.0 [...]