From owner-freebsd-multimedia@FreeBSD.ORG Tue Jun 23 21:38:48 2015 Return-Path: Delivered-To: freebsd-multimedia@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F3363609 for ; Tue, 23 Jun 2015 21:38:47 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from hub.freebsd.org (hub.freebsd.org [8.8.178.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hub.freebsd.org", Issuer "hub.freebsd.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CEAA2A47 for ; Tue, 23 Jun 2015 21:38:47 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: by hub.freebsd.org (Postfix) id C495F607; Tue, 23 Jun 2015 21:38:47 +0000 (UTC) Delivered-To: multimedia@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C07EA606; Tue, 23 Jun 2015 21:38:47 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59976A45; Tue, 23 Jun 2015 21:38:47 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: by wicnd19 with SMTP id nd19so118244825wic.1; Tue, 23 Jun 2015 14:38:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=COq1rS6DWw78vatgvw5CxUnGcOAgxYYQzGHWpNQHLIs=; b=rEzkpZq0XvQl5N/ILluIVfqa8YxdlpzfU/pfgWWq+xuL1zoaG6ClHQxw98bMYi90MF 5+27KfVugJh14Yus0senwEHnrUpxBWmhitbXK17IVRtLeEsZVpGC1Ru6eQNA+zFxzsZy lJUhC5yIlfdDZtFYXHw6o0g70NRp27rFT13Gn4od9AnhGTagudSmC/aSWEPcPTBfnzJP x721++fP2fOaVxAsMEioIeCp8slbz8NOq6CNq3nICjB06IiODs+wop8mYQNzhdhIUIpo A2qFm3x+vRxD70yU5HKNiWQWo8fAcnFMaQjZn9wBeA3VBxgtLGI2U7RgHJaqSRWNUxyL rWAg== MIME-Version: 1.0 X-Received: by 10.194.81.169 with SMTP id b9mr62761077wjy.126.1435095525636; Tue, 23 Jun 2015 14:38:45 -0700 (PDT) Sender: thomas.e.zander@googlemail.com Received: by 10.28.15.11 with HTTP; Tue, 23 Jun 2015 14:38:45 -0700 (PDT) In-Reply-To: References: Date: Tue, 23 Jun 2015 23:38:45 +0200 X-Google-Sender-Auth: vWrnnwtDQAJGtHFX0bh_GtCKfiw Message-ID: Subject: Re: ffmpeg26 confusion (Was: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED) From: Thomas Zander To: Jan Beich Cc: ports@freebsd.org, multimedia@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2015 21:38:48 -0000 On 23 June 2015 at 01:35, Jan Beich wrote: > (overquoting strawman ;) :-) > What happened to the schedule? 10.1 was released half a year ago and we're > approaching code freeze for 10.2. Not to mention packages for FreeBSD > releases are built against quaterly branches nowadays. And the next quaterly > is 2015Q3 which should happen in a week. It's a testament to the fact that no plan survives the first contact with reality. In lack of participation, I decided to hold off until I am in a position (time-wise) where I could deal with the fall-out of the upgrade for a couple of days without major interruption. Circumstances haven't been favourable so far. > Maybe do the following to improve the situation: > > (1) Update ffmpeg port to the latest version (2.7.1 currently) > (2) Remove ffmpeg26 port > (3) Add ffmpeg23 port with PORTSCOUT=limit:^2\.3.* > (4) Identify ports that hide ffmpeg dep behind an option > (5) Mass PORTREVISION bump in consumers (API/ABI changes in major versions) > (6) Exp-run with ffmpeg dep enabled if optional > (7) Fix bustage or convert to ffmpeg23 > (8) Remove ffmpeg23 if no consumers Yes, agreed, makes sense from today's point of view. When are you planning on getting started? :-) Riggs