Date: Tue, 16 Sep 2014 20:29:21 +0000 From: Max Brazhnikov <makc@freebsd.org> To: freebsd-ports@freebsd.org, multimedia@freebsd.org Cc: Thomas Zander <riggs@freebsd.org>, Michelle Sullivan <michelle@sorbs.net> Subject: Re: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED Message-ID: <17638075.cznnz2fj2I@mercury.ph.man.ac.uk> In-Reply-To: <CAFU734wKpEj9LCtAAq-h945td4CDAv_STLbbu_2Mhnm_K7KD%2Bw@mail.gmail.com> References: <CAFU734wG9rTaeZ5MMB8tvUYi0yHow1Wx5F9x-2c9rdF5SOTVeg@mail.gmail.com> <CAHtVNLPAUeA1qrnXn8UNADt_1p1o-bkxsnFU720U44_1Y8fSeg@mail.gmail.com> <CAFU734wKpEj9LCtAAq-h945td4CDAv_STLbbu_2Mhnm_K7KD%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Sep 2014 21:57:21 +0200 Thomas Zander wrote: > On 16 September 2014 21:08, William Grzybowski <wg@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17638075.cznnz2fj2I>