From: Koen Kooi <koen.kooi@linaro.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemd 208: move stray /usr/lib/systemd/* into /lib/systemd
Date: Tue, 21 Jan 2014 14:02:34 +0100 [thread overview]
Message-ID: <52DE6FEA.5070300@linaro.org> (raw)
In-Reply-To: <20140121130110.GC4100@jama>
On 01/21/2014 02:01 PM, Martin Jansa wrote:
> On Tue, Jan 21, 2014 at 12:01:21PM +0100, Koen Kooi wrote:
>> From: Koen Kooi <koen@dominion.thruhere.net>
>>
>> Apps testing for systemd config get confused when both /usr/lib/systemd and /lib/systemd exist. This fixes (among other things) dracut systemd detections.
>>
>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
>> ---
>> meta/recipes-core/systemd/systemd_208.bb | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_208.bb b/meta/recipes-core/systemd/systemd_208.bb
>> index 6590235..710624c 100644
>> --- a/meta/recipes-core/systemd/systemd_208.bb
>> +++ b/meta/recipes-core/systemd/systemd_208.bb
>> @@ -113,6 +113,12 @@ do_install() {
>>
>> # Delete journal README, as log can be symlinked inside volatile.
>> rm -f ${D}/${localstatedir}/log/README
>> +
>> + # fix up libdir confusion
>> + if [ -d ${D}${libdir}/systemd ] ; then
>> + cp -a ${D}${libdir}/systemd/* ${D}${systemd_unitdir}
>> + rm -rf ${D}${libdir}/systemd
>> + fi
>
> It's not your fault, but the indentation looks inconsistent with rest of
> do_install()
And I did especially pay attention to use tabs after all the meta-oe
patches I did :)
next prev parent reply other threads:[~2014-01-21 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 11:01 [PATCH] systemd 208: move stray /usr/lib/systemd/* into /lib/systemd Koen Kooi
2014-01-21 13:01 ` Martin Jansa
2014-01-21 13:02 ` Koen Kooi [this message]
2014-03-13 9:09 ` Koen Kooi
2014-03-14 1:41 ` Richard Purdie
2014-03-14 7:59 ` Koen Kooi
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=52DE6FEA.5070300@linaro.org \
--to=koen.kooi@linaro.org \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@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