From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] libsoup-2.4: disable libsoup-gnome by default
Date: Thu, 18 Feb 2016 22:54:09 +0000 [thread overview]
Message-ID: <1455836049.28376.99.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=WUd+Zi5feRe4iVShnkj5qdFHTPM42NCthbZc5-RrjcXg@mail.gmail.com>
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 libsoup-gnome-2.4 into it's own package, so that both
> libsoup-2.4 and libsoup-gnome-2.4 get renamed.
>
> 3) Use DEBIAN_NOAUTONAME to prevent renaming, even when the
> libsoup-2.4 package only contains one shared lib.
Probably 3) IMO, its what several other packages do.
> 4) Drop the gnome PACKAGECONFIG option so that people can't mess
> with it (in combination with one of the above).
Cheers,
Richard
next prev parent reply other threads:[~2016-02-18 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:21 [PATCH 0/2] libsoup-2.4: cleanup + disable libsoup-gnome by default Andre McCurdy
2016-02-18 19:21 ` [PATCH 1/2] libsoup-2.4: minor formatting improvements Andre McCurdy
2016-02-18 19:21 ` [PATCH 2/2] libsoup-2.4: disable libsoup-gnome by default Andre McCurdy
2016-02-18 19:39 ` Martin Jansa
2016-02-18 20:12 ` Andre McCurdy
2016-02-18 20:24 ` Paul Eggleton
2016-02-18 21:33 ` Andre McCurdy
2016-02-18 22:54 ` Richard Purdie [this message]
2016-02-18 23:44 ` Phil Blundell
2016-02-24 12:51 ` [PATCH 0/2] libsoup-2.4: cleanup + " Martin Jansa
2016-02-24 19:05 ` Andre McCurdy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455836049.28376.99.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox