On 07.08.2015 00:42, Luca Barbato wrote:
> On 06/08/15 23:26, Andreas Cadhalpun wrote:
>> I'm seeing more dramatic words than good arguments in your mail.
>
> Could we please tune it down a little?
Tell that wm4.
> For this release the deprecated APIs will be dropped w/out a third
> warning, if
On Fri, 7 Aug 2015 19:28:26 +0200
Dominik 'Rathann' Mierzejewski wrote:
> Hello,
>
> On Friday, 07 August 2015 at 15:36, wm4 wrote:
> > On Thu, 6 Aug 2015 23:26:05 +0200
> > Andreas Cadhalpun wrote:
> > > On 06.08.2015 00:53, wm4 wrote:
> [...]
> > > > Why do we have to suffer because Debian tr
Hello,
On Friday, 07 August 2015 at 15:36, wm4 wrote:
> On Thu, 6 Aug 2015 23:26:05 +0200
> Andreas Cadhalpun wrote:
> > On 06.08.2015 00:53, wm4 wrote:
[...]
> > > Why do we have to suffer because Debian tries to compile ancient
> > > releases against newer ffmpeg/libav releases? (How does that
On Thu, 6 Aug 2015 23:26:05 +0200
Andreas Cadhalpun wrote:
> On 06.08.2015 00:53, wm4 wrote:
> > Well, you sure like to list a lot of projects.
>
> No, I don't. I'd like it much more if the list was empty.
>
> > But what you don't say
> > is that many of these are either definitely dead (mplaye
On 06.08.2015 09:41, Hendrik Leppkes wrote:
> On Thu, Aug 6, 2015 at 3:32 AM, Michael Niedermayer
> wrote:
>> On Thu, Jul 30, 2015 at 05:05:12PM +0200, Andreas Cadhalpun wrote:
>> [...]
>>
>> IMO {
>>
>> trivial API, like identifers with different names or wrapers
>> that are identical except havi
On 05.08.2015 23:58, Luca Barbato wrote:
> On 05/08/15 21:31, Andreas Cadhalpun wrote:
>> On 04.08.2015 07:57, Reimar Döffinger wrote:
I do have on more proposal, but the problem is it needs someone to do the
work.
For each removed feature, prepare documentation "a monkey could foll
On 06.08.2015 00:53, wm4 wrote:
> Well, you sure like to list a lot of projects.
No, I don't. I'd like it much more if the list was empty.
> But what you don't say
> is that many of these are either definitely dead (mplayer2 comes to
> mind),
One is not many. But OK, let's get rid of mplayer2 [1
On Thu, Aug 06, 2015 at 09:41:54AM +0200, Hendrik Leppkes wrote:
> On Thu, Aug 6, 2015 at 3:32 AM, Michael Niedermayer
> wrote:
> > On Thu, Jul 30, 2015 at 05:05:12PM +0200, Andreas Cadhalpun wrote:
> > [...]
> >
> > IMO {
> >
> > trivial API, like identifers with different names or wrapers
> > th
On Thu, Aug 6, 2015 at 3:32 AM, Michael Niedermayer
wrote:
> On Thu, Jul 30, 2015 at 05:05:12PM +0200, Andreas Cadhalpun wrote:
> [...]
>
> IMO {
>
> trivial API, like identifers with different names or wrapers
> that are identical except having 1 argument less.
> That is API which does not requir
On Thu, 6 Aug 2015 03:32:39 +0200
Michael Niedermayer wrote:
> Its a bit unprofessional to break/remove API every 1-2 years
Great, then we can just drop the currently deprecated functions right
now.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Thu, Jul 30, 2015 at 05:05:12PM +0200, Andreas Cadhalpun wrote:
[...]
IMO {
trivial API, like identifers with different names or wrapers
that are identical except having 1 argument less.
That is API which does not require any testing to ensure its future
function and correctness, should be kep
On Wed, 5 Aug 2015 21:31:38 +0200
Andreas Cadhalpun wrote:
> On 04.08.2015 07:57, Reimar Döffinger wrote:
> > I do have on more proposal, but the problem is it needs someone to do the
> > work.
> > For each removed feature, prepare documentation "a monkey could follow" on
> > how
> > to replace
On 05.08.2015 22:07, Reimar Döffinger wrote:
> On 05.08.2015, at 21:31, Andreas Cadhalpun
> wrote:
>>> Btw. the magic option to enable compatibility is still somewhat useful as
>>> it lists
>>> and allows testing the specific changes that are coming up. But I agree
>>> it's only
>>> a minor hel
On 05.08.2015, at 21:31, Andreas Cadhalpun
wrote:
>> Btw. the magic option to enable compatibility is still somewhat useful as it
>> lists
>> and allows testing the specific changes that are coming up. But I agree it's
>> only
>> a minor help.
>
> The problem with such a magic option is that i
On 04.08.2015 07:57, Reimar Döffinger wrote:
> I do have on more proposal, but the problem is it needs someone to do the
> work.
> For each removed feature, prepare documentation "a monkey could follow" on how
> to replace it (you could call it a transition guide).
> Even better, a script that aut
On Tue, 4 Aug 2015 07:57:34 +0200
Reimar Döffinger wrote:
> On 31.07.2015, at 17:47, Nicolas George wrote:
> > I can propose the following middle term:
>
> I do have on more proposal, but the problem is it needs someone to do the
> work.
> For each removed feature, prepare documentation "a mon
On 31.07.2015, at 17:47, Nicolas George wrote:
> I can propose the following middle term:
I do have on more proposal, but the problem is it needs someone to do the work.
For each removed feature, prepare documentation "a monkey could follow" on how
to replace it (you could call it a transition g
On Thu, Jul 30, 2015 at 6:10 PM, Andreas Cadhalpun
wrote:
> Removing these APIs causes compile failures, which are more severe than
> occasional runtime failures. It means people have to use old versions of
> the libav* libraries.
I disagree as well, it's true that noone likes code failing to
com
On 30.07.2015, at 17:05, Andreas Cadhalpun
wrote:
> Hi,
>
> On 28.07.2015 15:36, Vittorio Giovara wrote:
>> This set contains the removal of all deprecated features marked as
>> such until 2012/early 2013. This was announced several times in the
>> past months and agreed at several meetings (si
On 31.07.2015, at 17:22, Hendrik Leppkes wrote:
> On Fri, Jul 31, 2015 at 5:12 PM, compn wrote:
>> On Thu, 30 Jul 2015 17:05:12 +0200
>> Andreas Cadhalpun wrote:
>>
>>> Hi,
>>>
>>> On 28.07.2015 15:36, Vittorio Giovara wrote:
This set contains the removal of all deprecated features marked
On Fri, Jul 31, 2015 at 5:47 PM, Nicolas George wrote:
> Le tridi 13 thermidor, an CCXXIII, Hendrik Leppkes a écrit :
>> They have had 2-3 years to update, what makes you think they will ever
>> if we don't force them at some point?
>
> What makes you think they will ever do it even if we try to f
Le tridi 13 thermidor, an CCXXIII, Hendrik Leppkes a écrit :
> They have had 2-3 years to update, what makes you think they will ever
> if we don't force them at some point?
What makes you think they will ever do it even if we try to force them? They
will just stick to an older version of FFmpeg,
On Fri, Jul 31, 2015 at 5:12 PM, compn wrote:
> On Thu, 30 Jul 2015 17:05:12 +0200
> Andreas Cadhalpun wrote:
>
>> Hi,
>>
>> On 28.07.2015 15:36, Vittorio Giovara wrote:
>> > This set contains the removal of all deprecated features marked as
>> > such until 2012/early 2013. This was announced sev
On Thu, 30 Jul 2015 17:05:12 +0200
Andreas Cadhalpun wrote:
> Hi,
>
> On 28.07.2015 15:36, Vittorio Giovara wrote:
> > This set contains the removal of all deprecated features marked as
> > such until 2012/early 2013. This was announced several times in the
> > past months and agreed at several
On 30.07.2015 18:26, Anton Khirnov wrote:
> Quoting Andreas Cadhalpun (2015-07-30 17:49:51)
>> I think that keeping some of these APIs "forever" is much less of a problem
>> then breaking the majority of reverse dependencies.
>
> The API breaks are not done for the fun of it.
I hope so. ;)
> The
On 30.07.2015 18:10, Luca Barbato wrote:
> On 30/07/15 17:49, Andreas Cadhalpun wrote:
>> Have you tried sending them patches before breaking compatibility?
>
> We did in the past.
Great, so please do it again.
> Needless to say distributors then did not pick up the updated releases
> of those s
On 30.07.2015 18:00, Hendrik Leppkes wrote:
> Patching dozens of downstream projects is clearly not in the scope of what
> should be expected from any Libav or FFmpeg developer.
But keeping the API usable is. Regularly breaking the majority of reverse
dependencies makes an API much less usable.
S
Am 30.07.2015 17:50 schrieb "Andreas Cadhalpun" <
andreas.cadhal...@googlemail.com>:
>
> On 30.07.2015 17:38, Anton Khirnov wrote:
> > Quoting Andreas Cadhalpun (2015-07-30 17:05:12)
> >> Ideally you should make sure that patches for all of them are
available,
> >> before these APIs get removed.
>
On 30.07.2015 17:38, Anton Khirnov wrote:
> Quoting Andreas Cadhalpun (2015-07-30 17:05:12)
>> Ideally you should make sure that patches for all of them are available,
>> before these APIs get removed.
>>
>> Considering how widespread the use of FF_API_PIX_FMT and FF_API_AVFRAME_LAVC
>> still is, i
Hi,
On 28.07.2015 15:36, Vittorio Giovara wrote:
> This set contains the removal of all deprecated features marked as
> such until 2012/early 2013. This was announced several times in the
> past months and agreed at several meetings (since fosdem and recently
> at the sprint).
>
> With more than
30 matches
Mail list logo
