Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/7] libinput: fix udevdir
Date: Tue, 26 Jul 2016 08:49:45 +0800	[thread overview]
Message-ID: <5796B3A9.4000809@windriver.com> (raw)
In-Reply-To: <CAJTo0LaAduh5ep=xgK8NO1MHc0R1Cr-Hwqe8Ut1FrkCviv+Rpg@mail.gmail.com>



On 07/26/2016 12:55 AM, Burton, Ross wrote:
>
> On 25 July 2016 at 08:28, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
>     +FILES_${PN} += "${base_libdir}/udev/ ${nonarch_base_libdir}/udev/"
>
>
> Isn't this covered by the bitbake.conf change?

Hi Ross,

No, it is the subdir udev/rules.d in bitbake.conf:

${base_prefix}/lib/udev/rules.d ${prefix}/lib/udev/rules.d
${base_libdir}/udev/rules.d ${libdir}/udev/rules.d

I'd like to update bitbake.conf to lib/udev (no rules.d) if no objections,
then we can drop this patch.

// Robert

>
> Ross
>


  reply	other threads:[~2016-07-26  0:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  7:28 [PATCH 0/7] Fix udev dirs Robert Yang
2016-07-25  7:28 ` [PATCH 1/7] bitbake.conf: add eudev's udevdir to FILES_${PN} Robert Yang
2016-07-25  7:28 ` [PATCH 2/7] systemd: install udev.pc Robert Yang
2016-07-25  7:28 ` [PATCH 3/7] libinput: fix udevdir Robert Yang
2016-07-25 16:55   ` Burton, Ross
2016-07-26  0:49     ` Robert Yang [this message]
2016-07-26 14:43       ` Burton, Ross
2016-07-25  7:28 ` [PATCH 4/7] ofono: remove duplicated udev setting from FILES_${PN} Robert Yang
2016-07-25  7:28 ` [PATCH 5/7] mdadm: " Robert Yang
2016-07-25  7:28 ` [PATCH 6/7] xf86-input-vmmouse: " Robert Yang
2016-07-25  7:28 ` [PATCH 7/7] eudev: don't move udev directory Robert Yang

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=5796B3A9.4000809@windriver.com \
    --to=liezhi.yang@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