[RFC PATCH] GStreamer 1.x support for Pidgin 2.x

[Jorge Villaseñor]

On Thu, Mar 19, 2015 at 5:11 PM, Jorge Villaseñor <salinasv at gmail.com>
wrote:

> Could we use this "gstreamer 0.10 is dead" to force developers to actively
> use main and get 3.0.0 done?
>
> I mean,
>
> On Thu, Mar 12, 2015 at 5:10 AM, David Woodhouse <dwmw2 at infradead.org>
> wrote:
>
>> GStreamer 0.10 is dead and no longer being maintained. Distributions
>> really want to kill it and stop shipping it in their default
>> installations. This adds the facility to build Pidgin 2.x against
>> GStreamer 1.x instead, thus causing much rejoicing.
>>
>
> Could we use this "gstreamer 0.10 is dead" to force developers to actively
> use main and get 3.0.0 done?
>
> I mean, not merging this so we force ourself to just release.
>
>
>
>> Obviously you can still build against 0.10. Even trunk retains that
>> option, although I'm not entirely sure why.
>>
>> This basically resyncs the fs2 code with trunk, including one or two
>> other improvements like the error handling. Largely based on work by
>> Michael Cronenworth.
>>
> <snip>
>>
>
>
Maybe this deprecation is not a good choice because the patch is already
done and I don't want to waste anyone's work. But maybe for the next
deprecation or feature we want.


> --
> Masca
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
>



-- 
Masca

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pidgin.im/pipermail/devel/attachments/20150319/eeabec19/attachment-0001.html>