On Thu, 2016-02-18 at 13:33 -0800, Andre McCurdy wrote:
> Aside from automated detection of such problems, what's the best fix
> in this particular case?
>
> 1) Use LEAD_SONAME to force renaming, even in the case when the
> libsoup-2.4 package contains both shared libs.
>
> 2) Split
On Thu, 2016-02-18 at 13:33 -0800, Andre McCurdy wrote:
> Aside from automated detection of such problems, what's the best fix
> in this particular case?
>
> 1) Use LEAD_SONAME to force renaming, even in the case when the
> libsoup-2.4 package contains both shared libs.
>
> 2) Split
On Thu, Feb 18, 2016 at 12:24 PM, Paul Eggleton
wrote:
> Hi Martin,
>
> On Thu, 18 Feb 2016 20:39:08 Martin Jansa wrote:
>> IIRC this will rename the resulting package (because there will be only one
>> shared library now).
>>
>> that will probably break on device
Hi Martin,
On Thu, 18 Feb 2016 20:39:08 Martin Jansa wrote:
> IIRC this will rename the resulting package (because there will be only one
> shared library now).
>
> that will probably break on device upgrade-path
>
> I'm not sure if someone still cares about upgrade-paths.. there are too
> many
On Thu, Feb 18, 2016 at 11:39 AM, Martin Jansa wrote:
> IIRC this will rename the resulting package (because there will be only one
> shared library now).
Yes, you're right. Previously "libsoup-2.4" and becomes
"libsoup-2.4-1" when the "gnome" PACKAGECONFIG is removed.
>
IIRC this will rename the resulting package (because there will be only one
shared library now).
that will probably break on device upgrade-path
I'm not sure if someone still cares about upgrade-paths.. there are too
many issues going in unnoticed.
On Thu, Feb 18, 2016 at 8:21 PM, Andre McCurdy
libsoup-gnome is entirely deprecated and has just been stubs since 2.42.
Signed-off-by: Andre McCurdy
---
meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git