From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/7] bitbake.conf: add systemd_unitdir
Date: Thu, 22 Mar 2012 10:57:08 -0700 [thread overview]
Message-ID: <4F6B67F4.6010000@linux.intel.com> (raw)
In-Reply-To: <1332414362-6406-1-git-send-email-schnitzeltony@googlemail.com>
On 03/22/2012 04:05 AM, Andreas Müller wrote:
> Some of oe-core's recipes need to know where systemd units are. Since the
> directory might change in the future [1], we set the location once globally to
> reduce maintenance efforts
>
> [1] http://www.gossamer-threads.com/lists/gentoo/dev/245758
>
> Signed-off-by: Andreas Müller<schnitzeltony@googlemail.com>
> ---
> meta/conf/bitbake.conf | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 07982d7..52802f6 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -39,6 +39,7 @@ export libexecdir = "${exec_prefix}/libexec"
> export libdir = "${exec_prefix}/${baselib}"
> export includedir = "${exec_prefix}/include"
> export oldincludedir = "${exec_prefix}/include"
> +export systemd_unitdir = "${base_libdir}/systemd"
>
> # Linkage between native/cross/nativesdk layouts
> base_bindir_native = "/bin"
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-22 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 11:05 [PATCH 1/7] bitbake.conf: add systemd_unitdir Andreas Müller
2012-03-22 11:05 ` [PATCH 2/7] avahi.inc: use systemd_unitdir Andreas Müller
2012-03-22 11:05 ` [PATCH 3/7] bluez4: " Andreas Müller
2012-03-22 11:05 ` [PATCH 4/7] ofono: " Andreas Müller
2012-03-22 11:06 ` [PATCH 5/7] dbus: " Andreas Müller
2012-03-22 11:06 ` [PATCH 6/7] alsa-utils: " Andreas Müller
2012-03-22 11:06 ` [PATCH 7/7] consolekit: " Andreas Müller
2012-03-22 14:22 ` [PATCH 1/7] bitbake.conf: add systemd_unitdir Martin Jansa
2012-03-22 17:57 ` Saul Wold [this message]
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=4F6B67F4.6010000@linux.intel.com \
--to=sgw@linux.intel.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