From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Cc: Ross Burton <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 0/2] Move systemd binaries to /sbin/systemd
Date: Mon, 15 Apr 2013 13:00:28 +0200 [thread overview]
Message-ID: <lyli8k12k3.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <cover.1365697555.git.ross.burton@intel.com> (Ross Burton's message of "Thu, 11 Apr 2013 17:28:24 +0100")
Ross Burton <ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:
> Following the example set by udev, move the binaries to /sbin/systemd
> and hardcode less paths in general. Tested on atom-pc with a .hddimg
> so the live boot/initrd paths were tested.
At least the moving of udev breaks a lot of local recipes here which
install e.g. local rules or keymaps in /lib/udev. This is a silent break
which is detected at device runtime only. The global 'bitbake.conf' has
not been updated for the new paths neither.
There should be:
1. added some QA checks which detect this broken packaging
2. added some global variables (e.g. 'udev_basedir') which can be used
in the rules.
Enrico
next prev parent reply other threads:[~2013-04-15 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 16:28 [PATCH 0/2] Move systemd binaries to /sbin/systemd Ross Burton
2013-04-11 16:28 ` [PATCH 1/2] systemd: move the " Ross Burton
2013-04-11 16:28 ` [PATCH 2/2] initrdscripts: look for new systemd-udevd location Ross Burton
2013-04-15 11:00 ` Enrico Scholz [this message]
2013-04-15 11:21 ` [PATCH 0/2] Move systemd binaries to /sbin/systemd Koen Kooi
2013-04-15 15:15 ` Richard Purdie
2013-04-15 15:58 ` Enrico Scholz
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=lyli8k12k3.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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