From: George Dunlap <george.dunlap@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH 2/5] raisin: Detect systemd
Date: Wed, 14 Oct 2015 17:34:03 +0100 [thread overview]
Message-ID: <561E83FB.9040703@citrix.com> (raw)
In-Reply-To: <1444839707-2339-3-git-send-email-george.dunlap@eu.citrix.com>
On 14/10/15 17:21, George Dunlap wrote:
> Add systemd development libraries if we detect systemd present on the system
>
> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
Sorry, meant to add a comment here...
> ---
> components/xen | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/components/xen b/components/xen
> index 090cceb..93ed288 100644
> --- a/components/xen
> +++ b/components/xen
> @@ -8,6 +8,11 @@ function xen_check_package() {
> local DEP_Debian_common="build-essential python-dev gettext uuid-dev \
> libncurses5-dev libyajl-dev libaio-dev pkg-config libglib2.0-dev \
> libssl-dev libpixman-1-dev bridge-utils wget"
> +
> + if [[ -e "/usr/lib/systemd" ]]
> + then
> + DEP_Debian_common="$DEP_Debian_common libsystemd-daemon-dev"
> + fi
> local DEP_Debian_x86_32="$DEP_Debian_common bcc iasl bin86 texinfo"
> local DEP_Debian_x86_64="$DEP_Debian_x86_32 libc6-dev-i386"
> local DEP_Debian_arm32="$DEP_Debian_common libfdt-dev"
> @@ -16,6 +21,10 @@ function xen_check_package() {
> local DEP_Fedora_common="make gcc python-devel gettext libuuid-devel \
> ncurses-devel glib2-devel libaio-devel openssl-devel yajl-devel \
> patch pixman-devel glibc-devel bridge-utils grub2 wget tar bzip2"
> + if [[ -e "/usr/lib/systemd" ]]
> + then
> + DEP_Fedora_common="$DEP_Fedora_common systemd-devel|systemd-container-devel"
> + fi
This is a bit dodgy, as basically CentOS (and I think Fedora) have
separate packages for systemd when inside a container vs on real
hardware. But unfortunately I'm not sure there's a way to make yum
smart enough to know, "Gee, I'm in a container, I should run systemd
instead".
Having the "alias" like this allows the user to work around it by
manually installing systemd-container-devel. It's not great though,
because there's still nothing to prompt the user to install the correct
package.
Also...
> local DEP_Fedora_x86_32="$DEP_Fedora_common dev86 acpica-tools texinfo"
> local DEP_Fedora_x86_64="$DEP_Fedora_x86_32 glibc-devel.i686"
>
> @@ -23,6 +32,7 @@ function xen_check_package() {
> local DEP_CentOS_x86_32="$DEP_CentOS_common dev86 texinfo iasl"
> local DEP_CentOS_x86_64="$DEP_CentOS_x86_32 glibc-devel.i686"
>
> +
Oops.
-George
next prev parent reply other threads:[~2015-10-14 16:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 16:21 [PATCH 0/5] raisin: Miscelaneous improvements George Dunlap
2015-10-14 16:21 ` [PATCH 1/5] raisin: Handle aliases for packages, add pciutils-dev / libpci-dev alias George Dunlap
2015-10-16 13:37 ` Stefano Stabellini
2015-10-19 9:52 ` George Dunlap
2015-10-14 16:21 ` [PATCH 2/5] raisin: Detect systemd George Dunlap
2015-10-14 16:34 ` George Dunlap [this message]
2015-10-16 13:41 ` Stefano Stabellini
2015-10-19 9:54 ` George Dunlap
2015-10-19 11:09 ` Stefano Stabellini
2015-10-16 13:39 ` Stefano Stabellini
2015-10-16 14:02 ` Ian Campbell
2015-10-16 14:04 ` Stefano Stabellini
2015-10-19 10:01 ` George Dunlap
2015-10-19 11:15 ` Stefano Stabellini
2015-10-14 16:21 ` [PATCH 3/5] raisin: Allow iasl to alias acpica-tools, unify Fedora and CentOS deps for xen George Dunlap
2015-10-16 13:42 ` Stefano Stabellini
2015-10-14 16:21 ` [PATCH 4/5] raisin: Change update/release parsing OSes George Dunlap
2015-10-16 13:49 ` Stefano Stabellini
2015-10-19 9:16 ` George Dunlap
2015-10-19 11:26 ` Stefano Stabellini
2015-10-19 11:39 ` George Dunlap
2015-10-14 16:21 ` [PATCH 5/5] raisin: Add XEN_CONFIG_EXTRA to config file George Dunlap
2015-10-16 13:53 ` Stefano Stabellini
2015-10-19 9:24 ` George Dunlap
2015-10-19 11:37 ` Stefano Stabellini
2015-10-19 11:42 ` George Dunlap
2015-10-19 11:49 ` Stefano Stabellini
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=561E83FB.9040703@citrix.com \
--to=george.dunlap@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).