RFC News item: FFmpeg default

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

RFC News item: FFmpeg default

Ben de Groot-2
Title: FFmpeg default
Author: Ben de Groot <[hidden email]>
Content-Type: text/plain
Posted: 2015-04-01
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: virtual/ffmpeg

Since the choice between ffmpeg and libav has been made more
explicit, there has been a lot of discussion about what the
default implementation should be. It can be concluded that
media-video/ffmpeg has wider support, and would be somewhat
more convenient for most end-users.

For this reason the default implementation has been switched
back from media-video/libav to media-video/ffmpeg by removing
the libav useflag from the base profile.

If the libav useflag is already globally enabled or disabled
in /etc/portage/make.conf, then no further action is required.

Users who implicitly relied on libav being enabled in their
profile, and who wish to continue using libav, should enable
this in their local /etc/portage configuration.


--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Michał Górny-5
Dnia 2015-03-30, o godz. 00:07:16
Ben de Groot <[hidden email]> napisał(a):

> Title: FFmpeg default
> Author: Ben de Groot <[hidden email]>
> Content-Type: text/plain
> Posted: 2015-04-01
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: virtual/ffmpeg
>
> Since the choice between ffmpeg and libav has been made more
> explicit, there has been a lot of discussion about what the
> default implementation should be. It can be concluded that
> media-video/ffmpeg has wider support, and would be somewhat
> more convenient for most end-users.
>
> For this reason the default implementation has been switched
> back from media-video/libav to media-video/ffmpeg by removing
> the libav useflag from the base profile.
>
> If the libav useflag is already globally enabled or disabled
> in /etc/portage/make.conf, then no further action is required.
>
> Users who implicitly relied on libav being enabled in their
> profile, and who wish to continue using libav, should enable
> this in their local /etc/portage configuration.
Include example code.

Also please prepare an update to the USE=libav news item to state
updated default.

--
Best regards,
Michał Górny

attachment0 (968 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Peter Stuge-4
In reply to this post by Ben de Groot-2
Ben de Groot wrote:
> Title: FFmpeg default
> Posted: 2015-04-01

Bad date for such news.


//Peter

Reply | Threaded
Open this post in threaded view
|

回复:Re: [gentoo-dev] RFC News item: FFmpeg default

Nicol TAO
so. believe it or not?

在2015年03月30日 01:02,[hidden email] 写道:
Ben de Groot wrote:
> Title: FFmpeg default
> Posted: 2015-04-01

Bad date for such news.


//Peter



Reply | Threaded
Open this post in threaded view
|

Re: 回复:Re: [gentoo-dev] RFC News item: FFmpeg default

Peter Stuge-4
Nicol TAO wrote:
> so. believe it or not?

Communication should reduce confusion, not risk increasing it.


//Peter

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Ben de Groot-2
In reply to this post by Michał Górny-5
On 30 March 2015 at 00:23, Michał Górny <[hidden email]> wrote:
> Dnia 2015-03-30, o godz. 00:07:16
>
> Include example code.
>

Updated version:

Title: FFmpeg default
Author: Ben de Groot <[hidden email]>
Content-Type: text/plain
Posted: 2015-04-07
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: media-video/ffmpeg
Display-If-Installed: media-video/libav

Since the choice between ffmpeg and libav has been made more
explicit, there has been a lot of discussion about what the
default implementation should be. It can be concluded that
media-video/ffmpeg has wider support, and would be somewhat
more convenient for most end-users.

For this reason the default implementation has been switched
back from media-video/libav to media-video/ffmpeg by removing
the libav useflag from the base profile.

If the libav useflag is already globally enabled or disabled
in /etc/portage/make.conf, then no further action is required.

Users who implicitly relied on libav being enabled in their
profile, and who wish to continue using libav, should enable
USE=libav in their /etc/portage/make.conf file.

> Also please prepare an update to the USE=libav news item to state
> updated default.

Diff:

--- /var/portage/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
2015-02-04 05:31:20.000000000 +0800
+++ /home/ben/tmp/2015-02-01-use-libav.en.txt   2015-04-06
14:05:56.982039939 +0800
@@ -2,7 +2,7 @@
 Author: Michał Górny <[hidden email]>
 Content-Type: text/plain
 Posted: 2015-02-01
-Revision: 1
+Revision: 2
 News-Item-Format: 1.0
 Display-If-Installed: media-video/ffmpeg
 Display-If-Installed: media-video/libav
@@ -20,17 +20,17 @@
 However, whenever appropriate additional USE=libav will be introduced to
 control the preference of one implementation over the other.

-Users who currently use libav (the Gentoo default) do not have to
-perform any action since USE=libav is enabled by default. It should be
-noted that the users still need to enable USE=ffmpeg on packages with
-optional libav support as well. Users who want to use ffmpeg instead
-need to specify USE=-libav in make.conf explicitly.
+Users who currently use libav need to enable USE=libav in
+/etc/portage/make.conf. It should be noted that users still need to
+enable USE=ffmpeg on packages with optional libav support as well.
+Users who currently use ffmpeg need to take no action.

 Please also note that some packages support only one of the two
 implementations. An attempt to install one of those packages may result
 in blockers requiring the user changes the global USE=libav state.
 The most notable example of such package is media-video/mplayer.
-media-video/mpv may be used as a replacement for users who prefer libav.
+media-video/mpv may be used as a replacement for users who prefer libav,
+even though upstream mpv developers recommend using ffmpeg.

 Please do not alter the state of 'libav' flag on a per-package basis
 (e.g. via package.use). The flag needs to be set globally to have


--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Michał Górny-5
Dnia 2015-04-06, o godz. 14:10:12
Ben de Groot <[hidden email]> napisał(a):

> On 30 March 2015 at 00:23, Michał Górny <[hidden email]> wrote:
> > Dnia 2015-03-30, o godz. 00:07:16
> >
> > Include example code.
> >
>
> Updated version:
>
> Title: FFmpeg default
> Author: Ben de Groot <[hidden email]>
> Content-Type: text/plain
> Posted: 2015-04-07
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: media-video/ffmpeg
> Display-If-Installed: media-video/libav
>
> Since the choice between ffmpeg and libav has been made more
> explicit, there has been a lot of discussion about what the
> default implementation should be. It can be concluded that
> media-video/ffmpeg has wider support, and would be somewhat
> more convenient for most end-users.
>
> For this reason the default implementation has been switched
> back from media-video/libav to media-video/ffmpeg by removing
> the libav useflag from the base profile.
'Switched back' is suggesting there was some 'unintentional' switch
from ffmpeg to libav. Keep this free of politics, and just 'switched'.

> If the libav useflag is already globally enabled or disabled
> in /etc/portage/make.conf, then no further action is required.
>
> Users who implicitly relied on libav being enabled in their
> profile, and who wish to continue using libav, should enable
> USE=libav in their /etc/portage/make.conf file.
>
> > Also please prepare an update to the USE=libav news item to state
> > updated default.
>
> Diff:
>
> --- /var/portage/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
> 2015-02-04 05:31:20.000000000 +0800
> +++ /home/ben/tmp/2015-02-01-use-libav.en.txt   2015-04-06
> 14:05:56.982039939 +0800
> @@ -2,7 +2,7 @@
>  Author: Michał Górny <[hidden email]>
>  Content-Type: text/plain
>  Posted: 2015-02-01
> -Revision: 1
> +Revision: 2
>  News-Item-Format: 1.0
>  Display-If-Installed: media-video/ffmpeg
>  Display-If-Installed: media-video/libav
> @@ -20,17 +20,17 @@
>  However, whenever appropriate additional USE=libav will be introduced to
>  control the preference of one implementation over the other.
>
> -Users who currently use libav (the Gentoo default) do not have to
> -perform any action since USE=libav is enabled by default. It should be
> -noted that the users still need to enable USE=ffmpeg on packages with
> -optional libav support as well. Users who want to use ffmpeg instead
> -need to specify USE=-libav in make.conf explicitly.
> +Users who currently use libav need to enable USE=libav in
> +/etc/portage/make.conf. It should be noted that users still need to
> +enable USE=ffmpeg on packages with optional libav support as well.
> +Users who currently use ffmpeg need to take no action.
>
>  Please also note that some packages support only one of the two
>  implementations. An attempt to install one of those packages may result
>  in blockers requiring the user changes the global USE=libav state.
>  The most notable example of such package is media-video/mplayer.
> -media-video/mpv may be used as a replacement for users who prefer libav.
> +media-video/mpv may be used as a replacement for users who prefer libav,
> +even though upstream mpv developers recommend using ffmpeg.
This is off-topic, and strongly biased.

>  Please do not alter the state of 'libav' flag on a per-package basis
>  (e.g. via package.use). The flag needs to be set globally to have

FYI: since Council's meeting in one week, I have added this to
the agenda. I'm really concerned about Gentoo's PR when users suffer
due to developers ping-ponging implementations/defaults.

--
Best regards,
Michał Górny

attachment0 (968 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Ben de Groot-2
On 6 April 2015 at 17:35, Michał Górny <[hidden email]> wrote:

> Dnia 2015-04-06, o godz. 14:10:12
> Ben de Groot <[hidden email]> napisał(a):
>
>> On 30 March 2015 at 00:23, Michał Górny <[hidden email]> wrote:
>> > Dnia 2015-03-30, o godz. 00:07:16
>> >
>> > Include example code.
>> >
>>
>> Updated version:
>>
>> Title: FFmpeg default
>> Author: Ben de Groot <[hidden email]>
>> Content-Type: text/plain
>> Posted: 2015-04-07
>> Revision: 1
>> News-Item-Format: 1.0
>> Display-If-Installed: media-video/ffmpeg
>> Display-If-Installed: media-video/libav
>>
>> Since the choice between ffmpeg and libav has been made more
>> explicit, there has been a lot of discussion about what the
>> default implementation should be. It can be concluded that
>> media-video/ffmpeg has wider support, and would be somewhat
>> more convenient for most end-users.
>>
>> For this reason the default implementation has been switched
>> back from media-video/libav to media-video/ffmpeg by removing
>> the libav useflag from the base profile.
>
> 'Switched back' is suggesting there was some 'unintentional' switch
> from ffmpeg to libav. Keep this free of politics, and just 'switched'.

No, it does not suggest that. It simply reflects the history of the
issue: once upon a time we had ffmpeg. Then libav was introduced and
at some point made the default implementation. Now we are switching
back to ffmpeg as default implementation. There is no politics in my
statement.

>> If the libav useflag is already globally enabled or disabled
>> in /etc/portage/make.conf, then no further action is required.
>>
>> Users who implicitly relied on libav being enabled in their
>> profile, and who wish to continue using libav, should enable
>> USE=libav in their /etc/portage/make.conf file.
>>
>> > Also please prepare an update to the USE=libav news item to state
>> > updated default.
>>
>> Diff:
>>
>> --- /var/portage/metadata/news/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
>> 2015-02-04 05:31:20.000000000 +0800
>> +++ /home/ben/tmp/2015-02-01-use-libav.en.txt   2015-04-06
>> 14:05:56.982039939 +0800
>> @@ -2,7 +2,7 @@
>>  Author: Michał Górny <[hidden email]>
>>  Content-Type: text/plain
>>  Posted: 2015-02-01
>> -Revision: 1
>> +Revision: 2
>>  News-Item-Format: 1.0
>>  Display-If-Installed: media-video/ffmpeg
>>  Display-If-Installed: media-video/libav
>> @@ -20,17 +20,17 @@
>>  However, whenever appropriate additional USE=libav will be introduced to
>>  control the preference of one implementation over the other.
>>
>> -Users who currently use libav (the Gentoo default) do not have to
>> -perform any action since USE=libav is enabled by default. It should be
>> -noted that the users still need to enable USE=ffmpeg on packages with
>> -optional libav support as well. Users who want to use ffmpeg instead
>> -need to specify USE=-libav in make.conf explicitly.
>> +Users who currently use libav need to enable USE=libav in
>> +/etc/portage/make.conf. It should be noted that users still need to
>> +enable USE=ffmpeg on packages with optional libav support as well.
>> +Users who currently use ffmpeg need to take no action.
>>
>>  Please also note that some packages support only one of the two
>>  implementations. An attempt to install one of those packages may result
>>  in blockers requiring the user changes the global USE=libav state.
>>  The most notable example of such package is media-video/mplayer.
>> -media-video/mpv may be used as a replacement for users who prefer libav.
>> +media-video/mpv may be used as a replacement for users who prefer libav,
>> +even though upstream mpv developers recommend using ffmpeg.
>
> This is off-topic, and strongly biased.

The original statement may give the impression that mpv is to libav
what mplayer is to ffmpeg. Many users were surprised to find out that
mpv upstream actually recommends ffmpeg, and that some of mpv's
features do not work with libav. If we are going to specifically
recommend mpv, then it is something users need to be aware of.

We could change it to: media-video/mpv works with both ffmpeg and
libav, though some of its features require ffmpeg. Or something along
those lines.

>>  Please do not alter the state of 'libav' flag on a per-package basis
>>  (e.g. via package.use). The flag needs to be set globally to have
>
> FYI: since Council's meeting in one week, I have added this to
> the agenda. I'm really concerned about Gentoo's PR when users suffer
> due to developers ping-ponging implementations/defaults.

It's not so much ping-ponging as stumbling upon what is the best
solution for our users. Some years ago libav was made a soft default.
And if I recall correctly, that was done with very little discussion.
Recently this default was made harder by adding USE=libav to the base
profile. This resulted in quite a backlash from users.

Moreover, many upstreams of consuming packages actually prefer ffmpeg.
Add to that the upstream ffmpeg policy of merging in changes from
libav.

All in all, from an end-user point of view it makes more sense to have
ffmpeg as default. And when users were asked, they overwhelmingly
expressed support for changing the default to ffmpeg.

I see no reason to stick with libav as default, except political
(which I'm trying to avoid here).

--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Alexis Ballier-2
On Tue, 7 Apr 2015 07:13:16 +0800
Ben de Groot <[hidden email]> wrote:

> >>  Please also note that some packages support only one of the two
> >>  implementations. An attempt to install one of those packages may
> >> result in blockers requiring the user changes the global USE=libav
> >> state. The most notable example of such package is
> >> media-video/mplayer. -media-video/mpv may be used as a replacement
> >> for users who prefer libav. +media-video/mpv may be used as a
> >> replacement for users who prefer libav, +even though upstream mpv
> >> developers recommend using ffmpeg.
> >
> > This is off-topic, and strongly biased.
>
> The original statement may give the impression that mpv is to libav
> what mplayer is to ffmpeg. Many users were surprised to find out that
> mpv upstream actually recommends ffmpeg, and that some of mpv's
> features do not work with libav. If we are going to specifically
> recommend mpv, then it is something users need to be aware of.
>
> We could change it to: media-video/mpv works with both ffmpeg and
> libav, though some of its features require ffmpeg. Or something along
> those lines.


I'd rather drop entirely that part about mplayer/mpv; I agree this is
something users need to be aware of if we recommend mpv but with ffmpeg
as default the "mplayer hard requires ffmpeg" is no longer an issue.
Otherwise, we might as well note that gst-libav recommends... heh...
libav, and as such all gst based players (totem, firefox, etc.)

Alexis.

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Ian Delaney-2
In reply to this post by Ben de Groot-2
On Tue, 7 Apr 2015 07:13:16 +0800
Ben de Groot <[hidden email]> wrote:

> On 6 April 2015 at 17:35, Michał Górny <[hidden email]> wrote:
> > Dnia 2015-04-06, o godz. 14:10:12
> > Ben de Groot <[hidden email]> napisał(a):
> >
> >> On 30 March 2015 at 00:23, Michał Górny <[hidden email]> wrote:
> >> > Dnia 2015-03-30, o godz. 00:07:16
> >> >
> >> > Include example code.
> >> >
> >>
> >> Updated version:
> >>
> >> Title: FFmpeg default
> >> Author: Ben de Groot <[hidden email]>
> >> Content-Type: text/plain
> >> Posted: 2015-04-07
> >> Revision: 1
> >> News-Item-Format: 1.0
> >> Display-If-Installed: media-video/ffmpeg
> >> Display-If-Installed: media-video/libav
> >>
> >> Since the choice between ffmpeg and libav has been made more
> >> explicit, there has been a lot of discussion about what the
> >> default implementation should be. It can be concluded that
> >> media-video/ffmpeg has wider support, and would be somewhat
> >> more convenient for most end-users.
> >>
> >> For this reason the default implementation has been switched
> >> back from media-video/libav to media-video/ffmpeg by removing
> >> the libav useflag from the base profile.
> >
> > 'Switched back' is suggesting there was some 'unintentional' switch
> > from ffmpeg to libav. Keep this free of politics, and just
> > 'switched'.
>
> No, it does not suggest that. It simply reflects the history of the
> issue: once upon a time we had ffmpeg. Then libav was introduced and
> at some point made the default implementation. Now we are switching
> back to ffmpeg as default implementation. There is no politics in my
> statement.
>
> >
> > This is off-topic, and strongly biased.
>
> The original statement may give the impression that mpv is to libav
> what mplayer is to ffmpeg. Many users were surprised to find out that
> mpv upstream actually recommends ffmpeg, and that some of mpv's
> features do not work with libav. If we are going to specifically
> recommend mpv, then it is something users need to be aware of.
>
> We could change it to: media-video/mpv works with both ffmpeg and
> libav, though some of its features require ffmpeg. Or something along
> those lines.
>
> >>  Please do not alter the state of 'libav' flag on a per-package
> >> basis (e.g. via package.use). The flag needs to be set globally to
> >> have
> >
> > FYI: since Council's meeting in one week, I have added this to
> > the agenda. I'm really concerned about Gentoo's PR when users suffer
> > due to developers ping-ponging implementations/defaults.
>

> It's not so much ping-ponging as stumbling upon what is the best
> solution for our users. Some years ago libav was made a soft default.
> And if I recall correctly, that was done with very little discussion.
> Recently this default was made harder by adding USE=libav to the base
> profile. This resulted in quite a backlash from users.
>
> Moreover, many upstreams of consuming packages actually prefer ffmpeg.
> Add to that the upstream ffmpeg policy of merging in changes from
> libav.
>
> All in all, from an end-user point of view it makes more sense to have
> ffmpeg as default. And when users were asked, they overwhelmingly
> expressed support for changing the default to ffmpeg.
>
> I see no reason to stick with libav as default, except political
> (which I'm trying to avoid here).
>

+1

--
kind regards

Ian Delaney

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Peter Stuge-4
In reply to this post by Ben de Groot-2
Ben de Groot wrote:
> I see no reason to stick with libav as default, except political
> (which I'm trying to avoid here).

It's very convenient to try to ignore politics, but IMO that's no
better in open source than on election day. A default is always a
political choice.

With any choice, the mainstream option is obviously more convenient,
but that doesn't make it right, only convenient. I've found that the
mainstream option is actually much more likely to be wrong.

To spell it out: I consider distributions to have a moral duty to
make informed political choices, also for overridable defaults, for
the benefit of users who don't bother making a choice themselves.

It's obvious that the world can be ruled with instant gratification.

It's further obvious to me that settling for what seems good in the
short-term may not really benefit anyone.

I think Gentoo needs to be explicitly and consciously political about
defaults. Competitors deserve no less than to be chosen or not chosen
based on their actual merits rather than popularity. Not making an
informed political choice is lame.

But whatever. Neither Gentoo nor the rest of the world runs on facts
or even right and wrong, so carry on. :)


//Peter

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Pacho Ramos
In reply to this post by Alexis Ballier-2
El mar, 07-04-2015 a las 09:00 +0200, Alexis Ballier escribió:
[...]
> I'd rather drop entirely that part about mplayer/mpv; I agree this is
> something users need to be aware of if we recommend mpv but with ffmpeg
> as default the "mplayer hard requires ffmpeg" is no longer an issue.
> Otherwise, we might as well note that gst-libav recommends... heh...
> libav, and as such all gst based players (totem, firefox, etc.)
>
> Alexis.
>

Well... for gst plugin we are anyway running in a "non-recommended" way
as soon as we don't run with its internal copy or the concrete libav
version each major gst-libav version is prepared to (like it's the case
currently with libav-9 for example or Debian with libav-11... and we are
the only two major distributions that are currently defaulting to libav
over ffmpeg ;)

Anyway, I agree that the mpv comment doesn't really belong to the news
item... if some mpv features won't work when built with "libav" it's up
to the ebuild to inform users about that problems (either with an ewarn
or with a local USE description for its "libav" flag)


Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Ben de Groot-2
In reply to this post by Alexis Ballier-2
On 7 April 2015 at 15:00, Alexis Ballier <[hidden email]> wrote:

> On Tue, 7 Apr 2015 07:13:16 +0800
> Ben de Groot <[hidden email]> wrote:
>
>> >>  Please also note that some packages support only one of the two
>> >>  implementations. An attempt to install one of those packages may
>> >> result in blockers requiring the user changes the global USE=libav
>> >> state. The most notable example of such package is
>> >> media-video/mplayer. -media-video/mpv may be used as a replacement
>> >> for users who prefer libav. +media-video/mpv may be used as a
>> >> replacement for users who prefer libav, +even though upstream mpv
>> >> developers recommend using ffmpeg.
>> >
>> > This is off-topic, and strongly biased.
>>
>> The original statement may give the impression that mpv is to libav
>> what mplayer is to ffmpeg. Many users were surprised to find out that
>> mpv upstream actually recommends ffmpeg, and that some of mpv's
>> features do not work with libav. If we are going to specifically
>> recommend mpv, then it is something users need to be aware of.
>>
>> We could change it to: media-video/mpv works with both ffmpeg and
>> libav, though some of its features require ffmpeg. Or something along
>> those lines.
>
>
> I'd rather drop entirely that part about mplayer/mpv; I agree this is
> something users need to be aware of if we recommend mpv but with ffmpeg
> as default the "mplayer hard requires ffmpeg" is no longer an issue.
> Otherwise, we might as well note that gst-libav recommends... heh...
> libav, and as such all gst based players (totem, firefox, etc.)
>
> Alexis.
>

Good point. So let's drop "The most notable example ..." until the end
of the paragraph.

And since this is now on the Council's agenda, we're waiting for their decision.

--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Ben de Groot-2
On 11 April 2015 at 15:19, Ben de Groot <[hidden email]> wrote:
>
> And since this is now on the Council's agenda, we're waiting for their decision.
>

Since the Council had no objections, this has now been committed.

Thanks for all the feedback.

--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Jason A. Donenfeld-3

https://lwn.net/Articles/650816/

On Apr 16, 2015 1:51 PM, "Ben de Groot" <[hidden email]> wrote:
On 11 April 2015 at 15:19, Ben de Groot <[hidden email]> wrote:
>
> And since this is now on the Council's agenda, we're waiting for their decision.
>

Since the Council had no objections, this has now been committed.

Thanks for all the feedback.

--
Cheers,

Ben | yngwin
Gentoo developer

Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Nikos Chantziaras-2
"he page you have tried to view (Why Debian returned to FFmpeg) is
currently available to LWN subscribers only."


On 14/07/15 14:12, Jason A. Donenfeld wrote:

> https://lwn.net/Articles/650816/
>
> On Apr 16, 2015 1:51 PM, "Ben de Groot" <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On 11 April 2015 at 15:19, Ben de Groot <[hidden email]
>     <mailto:[hidden email]>> wrote:
>      >
>      > And since this is now on the Council's agenda, we're waiting for
>     their decision.
>      >
>
>     Since the Council had no objections, this has now been committed.
>
>     Thanks for all the feedback.
>
>     --
>     Cheers,
>
>     Ben | yngwin
>     Gentoo developer
>



Reply | Threaded
Open this post in threaded view
|

Re: RFC News item: FFmpeg default

Dirkjan Ochtman-3
On Tue, Jul 14, 2015 at 1:49 PM, Nikos Chantziaras <[hidden email]> wrote:
> "The page you have tried to view (Why Debian returned to FFmpeg) is currently
> available to LWN subscribers only."

Here's a free link that everyone can access:

http://lwn.net/SubscriberLink/650816/3eb8dfcfbe81e7a7/

Cheers,

Dirkjan