Upload ptlib in unstable

[Eugen Dedu]

Hi Mark,

Do you speak about soname change?  Quoting from a private e-mail 
(14/04/2009), about a bug irrelevant to us moved to ptlib:
"> That was my reasoning when moving the bug to ptlib.

Understood, but things are not that simple. This is not a C library, in 
C++ you can have code from the library embedded in your application via 
the "inline" feature. Also one of the reasons that binary compatibility 
between libraries is virtually impossible, much the chagrin of most of 
the packagers, but that's just the way it is.'

Is that what you need?

Greetings to Kilian,
Eugen

Mark Purcell wrote:
> Eugen,
> 
> Do you know if this was ever brought up with ptlib upstream?
> 
> Kilian, who did a lot of the early work with ptlib was wondering on IRC.
> 
> Mark
> 
> 
> 
> On Tuesday 10 March 2009 03:51:40 Eugen Dedu wrote:
>> Hi,
>>
>> Something new about this proposed upload?
>>
>> =============
>>
>> Hi,
>>
>> Please upload the newest ptlib in unstable (or check it before too).  As
>> usually, the soname changed, so it should pass through the new queue.
>>
>> I had to remove dc and avc plugins, they do not compile anymore.  They
>> need a rewrite.  For info:
>>
>> "Just as an FYI Fedora has had AVC disabled for quite a while (since
>> well before ekiga 3) and had no bug reports or complaints." (from
>> http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00138.html
>> )
>>
>> As soon as ptlib is installed on all architectures, we can push opal too
>> (I have a small commit to do before).  I think it's better, elsewhere we
>> come again to the situation where opal was building and failed, because
>> ptlib had not yet been uploaded.