From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/9] systemd: remove hard-coded paths in FILES entries
Date: Thu, 3 Sep 2015 12:10:32 -0500 [thread overview]
Message-ID: <55E87F08.6020902@windriver.com> (raw)
In-Reply-To: <1441293176.24871.118.camel@linuxfoundation.org>
On 9/3/15 10:12 AM, Richard Purdie wrote:
> On Thu, 2015-09-03 at 15:58 +0100, Joshua Lock wrote:
>> Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk>
>> ---
>> meta/recipes-core/systemd/systemd_219.bb | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_219.bb b/meta/recipes-core/systemd/systemd_219.bb
>> index 4d32fd5..fbd86e8 100644
>> --- a/meta/recipes-core/systemd/systemd_219.bb
>> +++ b/meta/recipes-core/systemd/systemd_219.bb
>> @@ -306,10 +306,10 @@ FILES_${PN} = " ${base_bindir}/* \
>> ${exec_prefix}/lib/sysctl.d \
>> ${exec_prefix}/lib/sysusers.d \
>> ${localstatedir} \
>> - /lib/udev/rules.d/70-uaccess.rules \
>> - /lib/udev/rules.d/71-seat.rules \
>> - /lib/udev/rules.d/73-seat-late.rules \
>> - /lib/udev/rules.d/99-systemd.rules \
>> + ${base_libdir}/udev/rules.d/70-uaccess.rules \
>> + ${base_libdir}/udev/rules.d/71-seat.rules \
>> + ${base_libdir}/udev/rules.d/73-seat-late.rules \
>> + ${base_libdir}/udev/rules.d/99-systemd.rules \
>> "
>>
>> FILES_${PN}-dbg += "${rootlibdir}/.debug ${systemd_unitdir}/.debug ${systemd_unitdir}/*/.debug ${base_libdir}/security/.debug/"
>> @@ -327,7 +327,7 @@ RRECOMMENDS_${PN} += "systemd-serialgetty systemd-vconsole-setup \
>>
>> PACKAGES =+ "udev-dbg udev udev-hwdb"
>>
>> -FILES_udev-dbg += "/lib/udev/.debug"
>> +FILES_udev-dbg += "${base_libdir}/udev/.debug"
>
> From what I remember, this is intentional and this change likely breaks
> multilib. You don't want two sets of rules on a multilib system.
Correct.. it has to go into /lib or if everything is move to /usr, then /usr/lib.
--Mark
> Cheers,
>
> Richard
>
>
>
next prev parent reply other threads:[~2015-09-03 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 14:58 [PATCH 0/9] Fixes for a distro with a merged /usr Joshua Lock
2015-09-03 14:58 ` [PATCH 1/9] kmod: fix link creation when base_bindir != /bin Joshua Lock
2015-09-03 14:58 ` [PATCH 2/9] busybox: fixes for " Joshua Lock
2015-09-03 14:58 ` [PATCH 3/9] systemd: remove hard-coded paths in FILES entries Joshua Lock
2015-09-03 15:12 ` Richard Purdie
2015-09-03 15:22 ` Burton, Ross
2015-09-03 19:16 ` Joshua Lock
2015-09-03 17:10 ` Mark Hatle [this message]
2015-09-04 11:07 ` Joshua Lock
2015-09-04 14:06 ` Burton, Ross
2015-09-03 14:58 ` [PATCH 4/9] alsa-utils: handle udev dir being 2 levels below / Joshua Lock
2015-09-03 14:58 ` [PATCH 5/9] pulseaudio: " Joshua Lock
2015-09-03 14:58 ` [PATCH 6/9] bluez: " Joshua Lock
2015-09-03 14:58 ` [PATCH 7/9] pcmciautils: " Joshua Lock
2015-09-03 14:58 ` [PATCH 8/9] nfs-utils: don't force use of /sbin as sbindir Joshua Lock
2015-09-03 17:14 ` Mark Hatle
2015-09-03 19:15 ` Joshua Lock
2015-09-03 14:58 ` [PATCH 9/9] procps: fix for base_sbindir == sbindir Joshua Lock
2015-09-03 17:11 ` [PATCH 0/9] Fixes for a distro with a merged /usr Mark Hatle
2015-09-03 19:10 ` Joshua Lock
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=55E87F08.6020902@windriver.com \
--to=mark.hatle@windriver.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