Re: [gentoo-dev] ffmpeg vs libav choice of default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Whilst the default *is* still in place (and particularly after the recent news article detailing that users should be using libav), could we please keep commits like the following until *after* we've made an agreed upon decision please? http://so

Re: [gentoo-dev] Re: ffmpeg vs libav choice of default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya, On 06/02/15 08:48, Duncan wrote: > Daniel Campbell posted on Thu, 05 Feb 2015 22:55:05 -0800 as > excerpted: > >> As a user and prospective developer, why? Transparency is >> important to open communities like Gentoo's, and reading the >> discu

Re: [gentoo-dev] ffmpeg vs libav choice of default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya, On 06/02/15 11:49, Ben de Groot wrote: > Since we introduced the libav useflag, we have now a way to > finally make mpv-0.7* (using the upstream recommended ffmpeg as > default) visible to ~arch users, without the need to unmask it. > Users who

Re: [gentoo-dev] Re: ffmpeg vs libav choice of default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya, On 07/02/15 05:16, Ben de Groot wrote: > I discussed this beforehand with said developer on IRC. Ok, that wasn't clear from the commit message. > Do you think a news item to explain this situation and giving > explicit instructions for users w

Re: [gentoo-dev] .git folder getting mirrored to rsync mirrors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya, I also experienced this (on 2a01:488:67:1000:b01c:3277:0:1). It will also prevent portage from resyncing because it assumes the portage tree is under revision control (when there's just git directories, no actual data). It looks like infra are

<    1   2