From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Martin Jansa <martin.jansa@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] nss-myhostname: blacklist because of conflict with systemd
Date: Thu, 9 Oct 2014 17:38:35 +0800 [thread overview]
Message-ID: <5436579B.8090502@windriver.com> (raw)
In-Reply-To: <CAJTo0La4eAU8KbST6B6vLyxSLNs+df7e__mCdEYy4ssA7mu6Mw@mail.gmail.com>
On 10/07/2014 06:09 PM, Burton, Ross wrote:
> On 7 October 2014 02:12, Martin Jansa <martin.jansa@gmail.com> wrote:
>> +PNBLACKLIST[nss-myhostname] = "CONFLICT: systemd provides sysroots/qemux86-64/usr/lib/libnss_myhostname.so.2"
>
> How about we don't build throw a SkipPackage if nss-myhostname is
> building with the systemd DISTRO_FEATURE, as the conflict is because
> systemd has its own copy of nss-myhostname in the source tree?
>
Do you mean something like this ? I will send a patch for it and add Martin
in the CC list.
diff --git a/meta/recipes-support/nss-myhostname/nss-myhostname_0.3.bb
b/meta/recipes-support/nss-myhostname/nss-myhostname_0.3.bb
index 1237602..071e639 100644
--- a/meta/recipes-support/nss-myhostname/nss-myhostname_0.3.bb
+++ b/meta/recipes-support/nss-myhostname/nss-myhostname_0.3.bb
@@ -13,6 +13,12 @@ SRC_URI[sha256sum] =
"2ba744ea8d578d1c57c85884e94a3042ee17843a5294434d3a7f6c4d67
inherit autotools
+# The systemd has its own copy of nss-myhostname
+python () {
+ if bb.utils.contains ('DISTRO_FEATURES', 'systemd', True, False, d):
+ raise bb.parse.SkipPackage("'systemd' in DISTRO_FEATURES")
+}
+
pkg_postinst_${PN} () {
sed -e '/^hosts:/s/\s*\<myhostname\>//' \
-e 's/\(^hosts:.*\)\(\<files\>\)\(.*\)\(\<dns\>\)\(.*\)/\1\2
myhostname \3\4\5/' \
// Robert
> Ross
>
prev parent reply other threads:[~2014-10-09 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 1:12 [RFC][PATCH] nss-myhostname: blacklist because of conflict with systemd Martin Jansa
2014-10-07 10:09 ` Burton, Ross
2014-10-09 9:38 ` Robert Yang [this message]
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=5436579B.8090502@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.