From owner-freebsd-multimedia@FreeBSD.ORG Tue Sep 16 20:32:33 2014 Return-Path: Delivered-To: multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E59CBCB8; Tue, 16 Sep 2014 20:32:33 +0000 (UTC) Received: from mail.issp.ac.ru (mail.issp.ac.ru [77.236.34.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.issp.ac.ru", Issuer "relay.issp.ac.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3035790D; Tue, 16 Sep 2014 20:32:32 +0000 (UTC) Received: from [62.63.86.109] [62.63.86.109:6386] (HELO/EHLO mercury.ph.man.ac.uk, authenticated with PLAIN) by mail.issp.ac.ru with ESMTP/inet id s8GKTtrb007038 (using TLSv1/SSLv3, with cipher DHE-RSA-AES256-SHA (256 bits), verified NO) Wed, 17 Sep 2014 00:29:56 +0400 (MSK) X-Authentication-Warning: mail.issp.ac.ru: Host [62.63.86.109] claimed to be mercury.ph.man.ac.uk From: Max Brazhnikov To: freebsd-ports@freebsd.org, multimedia@freebsd.org Subject: Re: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED Date: Tue, 16 Sep 2014 20:29:21 +0000 Message-ID: <17638075.cznnz2fj2I@mercury.ph.man.ac.uk> User-Agent: KMail/4.12.5 (FreeBSD/9.3-STABLE; KDE/4.12.5; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: Thomas Zander , Michelle Sullivan X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 20:32:34 -0000 On Tue, 16 Sep 2014 21:57:21 +0200 Thomas Zander wrote: > On 16 September 2014 21:08, William Grzybowski wrote: > >>> 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. > >>> > >> > >> Any reason why you can't create an 'ffmpeg24' port so it can go live > >> then people can create a a port option to turn on using the later > >> version - then when the ports are all updated you can just 'switch it to > >> the default'... that seems to be the way the ports tree has been handled > >> over the last year. > > > > Or create a ffmpeg23 port and switch all ports that cant handle ffmpeg > > 2.4 to that before it happens. > > Thats how I handled the ffmpeg 0.x -> ffmpeg 2.x transition. It was > > very smooth, all things considered :). > > Given the fact that I still have ffmpeg0 installed, I'd say this > transition is not over :-) > Seriously, though, I am happy with pain-alleviating measures like > having a ffmpeg23 port for a short transition time. > What I want to avoid is that we all need to have 3 installations of > ffmpeg on the same machines for months or years and I think it's a > fair request to ask the maintainers to have a look sometime during the > next months. You can request an exp-run first, then depending on how many ports are affected either create ffmpeg23 or directly update the ffmpeg port. Max