Date: Tue, 16 Sep 2014 20:40:15 +0200 From: Thomas Zander <riggs@freebsd.org> To: ports@freebsd.org, multimedia@freebsd.org Subject: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED Message-ID: <CAFU734wG9rTaeZ5MMB8tvUYi0yHow1Wx5F9x-2c9rdF5SOTVeg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, if you maintain a port which uses directly or indirectly ffmpeg, i.e. it links to at least one of libavcodec libavdevice libavfilter libavformat libavresample libavutil please take a moment, this is important. Shortly after the release of FreeBSD 10.1 I plan to upgrade ffmpeg to the 2.4 branch and import the then-latest release from the 2.4 branch into the head of the ports tree. Unlike the recent upgrade from 2.2. to 2.3, this one will NOT be painless. ALL the mentioned libraries received a bump in their major version numbers, which means that they are not necessarily API compatible with the 2.3 series. In particular, this means that several APIs which have been deprecated several months/years ago(!) are really gone for good in 2.4. One prominent example for this is the removal of FF_API_CLOSE_INPUT_FILE in libavformat which breaks e.g. sox and transcode builds. In most cases (like the mentioned examples sox and transcode) a fix will be easy or even trivial, but you need to be proactive and take a look at it. I have prepared a drop-in replacement for the ffmpeg port which uses the recent 2.4 release. You can download it from: http://people.freebsd.org/~riggs/ffmpeg-2.4.tar.xz Please check whether the ports maintained by you build and link with this version and prepare a suitable fix if necessary. Thanks in advance and best regards Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFU734wG9rTaeZ5MMB8tvUYi0yHow1Wx5F9x-2c9rdF5SOTVeg>