xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, tim@xen.org, keir@xen.org,
	ian.campbell@citrix.com, jbeulich@suse.com
Subject: Re: [PATCH] xen: use XEN_BOOT_DIR as xen.gz install location
Date: Wed, 23 Apr 2014 10:09:23 +0200	[thread overview]
Message-ID: <53577533.9040905@citrix.com> (raw)
In-Reply-To: <1398240022-17570-1-git-send-email-olaf@aepfle.de>

On 23/04/14 10:00, Olaf Hering wrote:
> Xen is currently installed into /boot, which is a hardcoded path. This
> makes it impossible to install two xen.rpm packages from 'make rpmball'
> in parallel because rpm complains about conflicting files.
> Use XEN_BOOT_DIR to define the install path to make it possible to
> install xen.gz below --prefix=.
> 
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
>  xen/Makefile | 23 ++++++++++++-----------
>  1 file changed, 12 insertions(+), 11 deletions(-)
> 
> diff --git a/xen/Makefile b/xen/Makefile
> index 79fa8f2..fd82a94 100644
> --- a/xen/Makefile
> +++ b/xen/Makefile
> @@ -13,6 +13,7 @@ export BASEDIR := $(CURDIR)
>  export XEN_ROOT := $(BASEDIR)/..
>  
>  EFI_MOUNTPOINT ?= /boot/efi
> +XEN_BOOT_DIR ?= /boot

IMHO config/StdGNU.mk seems like a better place to put this.

  reply	other threads:[~2014-04-23  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  8:00 [PATCH] xen: use XEN_BOOT_DIR as xen.gz install location Olaf Hering
2014-04-23  8:09 ` Roger Pau Monné [this message]
2014-04-23  8:24   ` Olaf Hering
2014-04-23  9:37     ` Jan Beulich
2014-04-23  9:40       ` Olaf Hering
2014-04-23 11:33       ` Ian Campbell
2014-04-23 14:46         ` Roger Pau Monné
2014-04-23  9:34 ` Jan Beulich
2014-04-23  9:39   ` Olaf Hering
2014-04-23  9:47     ` Jan Beulich

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=53577533.9040905@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=olaf@aepfle.de \
    --cc=tim@xen.org \
    --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).