From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/7] pciutils: add PACKAGECONFIG for 'hwdb'
Date: Mon, 29 Dec 2014 19:48:05 +0800 [thread overview]
Message-ID: <54A13F75.6080908@windriver.com> (raw)
In-Reply-To: <CAJTo0Lay14Pytm5sHVBxqFmC5==abKa3M4o6Oc2Jef5L2FtYvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On 12/29/2014 07:45 PM, Burton, Ross wrote:
> Hi Chen,
>
> On 26 December 2014 at 09:35, Chen Qi <Qi.Chen@windriver.com
> <mailto:Qi.Chen@windriver.com>> wrote:
>
> Add PACKAGECONFIG for 'hwdb' to fix the following QA warning.
> WARNING: QA Issue: libpci rdepends on libudev, but it isn't a
> build dependency? [build-deps]
> WARNING: QA Issue: pciutils rdepends on libudev, but it isn't a
> build dependency? [build-deps]
>
>
> Respecting the systemd DISTRO_FEATURE to enable/disable the hwdb
> PACKAGECONFIG would make a lot of sense, can you send a patch?
>
> Ross
Yes.
The default value will be "hwdb" if 'systemd' is in distro features.
Regards,
Chen Qi
[-- Attachment #2: Type: text/html, Size: 2005 bytes --]
next prev parent reply other threads:[~2014-12-29 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 9:35 [PATCH 0/7] Package Upgrades Chen Qi
2014-12-26 9:35 ` [PATCH 1/7] kmod: upgrade to 19 Chen Qi
2014-12-26 9:35 ` [PATCH 2/7] tar: upgrade to 2.18 Chen Qi
2014-12-26 9:35 ` [PATCH 3/7] sudo: upgrade to latest state version 1.8.11p2 Chen Qi
2014-12-26 9:35 ` [PATCH 4/7] pciutils: upgrade to 3.3.0 Chen Qi
2014-12-26 9:35 ` [PATCH 5/7] pciutils: add PACKAGECONFIG for 'hwdb' Chen Qi
2014-12-29 11:45 ` Burton, Ross
2014-12-29 11:48 ` ChenQi [this message]
2014-12-26 9:35 ` [PATCH 6/7] xz: upgrade to latest stable release 5.2.0 Chen Qi
2014-12-26 9:35 ` [PATCH 7/7] grep: upgrade to 2.21 Chen Qi
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=54A13F75.6080908@windriver.com \
--to=qi.chen@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox