From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 2/3] libsoup-2.4: prevent PACKAGECONFIG dependant package renaming
Date: Thu, 18 Feb 2016 17:30:50 -0800 [thread overview]
Message-ID: <1455845451-25185-3-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1455845451-25185-1-git-send-email-armccurdy@gmail.com>
When built without gnome support, libsoup-2.4 will contain only one
shared lib and will therefore become subject to renaming by
debian.bbclass.
Prevent renaming in order to keep the package name consistent
regardless of whether gnome support is enabled or disabled.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb b/meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb
index 865c1d7..a9d8050 100644
--- a/meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb
+++ b/meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb
@@ -25,5 +25,11 @@ PACKAGECONFIG[gnome] = "--with-gnome,--without-gnome"
EXTRA_OECONF = "--disable-vala"
+# When built without gnome support, libsoup-2.4 will contain only one shared lib
+# and will therefore become subject to renaming by debian.bbclass. Prevent
+# renaming in order to keep the package name consistent regardless of whether
+# gnome support is enabled or disabled.
+DEBIAN_NOAUTONAME_${PN} = "1"
+
# glib-networking is needed for SSL, proxies, etc.
RRECOMMENDS_${PN} = "glib-networking"
--
1.9.1
next prev parent reply other threads:[~2016-02-19 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 1:30 [PATCH v2 0/3] libsoup-2.4: cleanup + disable libsoup-gnome by default Andre McCurdy
2016-02-19 1:30 ` [PATCH v2 1/3] libsoup-2.4: minor formatting improvements Andre McCurdy
2016-02-19 1:30 ` Andre McCurdy [this message]
2016-02-19 1:30 ` [PATCH v2 3/3] libsoup-2.4: disable libsoup-gnome by default 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=1455845451-25185-3-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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