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 nobody
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 follow on
how
to
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?
The summary so far is that the people in Libav do not want to do again
three time the extra miles.
This time will be up to the downstreams to take
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 follow on
how
to replace it (you could call it a
On 02/08/15 12:54, Janne Grunau wrote:
instead of deleting deprecated features keep them for another release
but hidden under a define like
AV_USE_REMOVED_FEATURES_WILL_BREAK_WITH_$VERSION_NEXT. That would result
in compile errors by default and gives hopefully enough motivation to
fix
On 2015-07-30 17:38:07 +0200, Anton Khirnov wrote:
Quoting Andreas Cadhalpun (2015-07-30 17:05:12)
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
On Thu, Jul 30, 2015 at 6:10 PM, Andreas Cadhalpun
andreas.cadhal...@googlemail.com 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
On Thu, 30 Jul 2015 17:05:12 +0200
Andreas Cadhalpun andreas.cadhal...@googlemail.com 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
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 two
Quoting Andreas Cadhalpun (2015-07-30 17:05:12)
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
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.
Considering
On 30/07/15 17:49, Andreas Cadhalpun wrote:
Have you tried sending them patches before breaking compatibility?
We did in the past.
Needless to say distributors then did not pick up the updated releases
of those softwares making it sort of a meaningless endeavor.
lu
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
Quoting Andreas Cadhalpun (2015-07-30 17:49:51)
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
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, it might
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.
So
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. ;)
There's a
Quoting Andreas Cadhalpun (2015-07-30 19:10:12)
On 30.07.2015 18:26, Anton Khirnov wrote:
There's a bunch of reasons why I think keeping them is a bad idea:
- some of the changes involve adding prefixes for proper namespacing, so
libav does not randomly conflict with other libraries.
On Wed, Jul 29, 2015 at 09:07:53AM +0200, Anton Khirnov wrote:
Quoting Kostya Shishkov (2015-07-29 08:59:42)
On Wed, Jul 29, 2015 at 08:44:48AM +0200, Anton Khirnov wrote:
Quoting Kostya Shishkov (2015-07-28 15:54:32)
On Tue, Jul 28, 2015 at 02:36:16PM +0100, Vittorio Giovara wrote:
On Wed, Jul 29, 2015 at 08:44:48AM +0200, Anton Khirnov wrote:
Quoting Kostya Shishkov (2015-07-28 15:54:32)
On Tue, Jul 28, 2015 at 02:36:16PM +0100, Vittorio Giovara wrote:
This set contains the removal of all deprecated features marked as
such until 2012/early 2013. This was announced
Quoting Kostya Shishkov (2015-07-28 15:54:32)
On Tue, Jul 28, 2015 at 02:36:16PM +0100, 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
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 two year span, downstream users should have had enough
time
On Tue, Jul 28, 2015 at 02:36:16PM +0100, 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
23 matches
Mail list logo
