Date: Tue, 16 Sep 2014 16:08:25 -0300 From: William Grzybowski <wg@freebsd.org> To: Michelle Sullivan <michelle@sorbs.net> Cc: Thomas Zander <riggs@freebsd.org>, "freebsd-ports@freebsd.org" <ports@freebsd.org>, multimedia@freebsd.org Subject: Re: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED Message-ID: <CAHtVNLPAUeA1qrnXn8UNADt_1p1o-bkxsnFU720U44_1Y8fSeg@mail.gmail.com> In-Reply-To: <541889F4.7080503@sorbs.net> References: <CAFU734wG9rTaeZ5MMB8tvUYi0yHow1Wx5F9x-2c9rdF5SOTVeg@mail.gmail.com> <541889F4.7080503@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 16, 2014 at 4:05 PM, Michelle Sullivan <michelle@sorbs.net> wrote: > Thomas Zander 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 :). -- William Grzybowski / wg FreeBSD Ports Committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHtVNLPAUeA1qrnXn8UNADt_1p1o-bkxsnFU720U44_1Y8fSeg>