xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] tools/mkrpm: allow custom rpm package name
Date: Wed, 30 Jul 2014 14:08:22 +0100	[thread overview]
Message-ID: <53D8EE46.9040400@eu.citrix.com> (raw)
In-Reply-To: <1406542747-9732-1-git-send-email-olaf@aepfle.de>

On 07/28/2014 11:19 AM, Olaf Hering wrote:
> Even if xen is configured and compiled with different --prefix= so that
> it operates entirely below $prefix, the resulting package from 'make
> rpmball' is always called "xen.rpm".
>
> Use an environment name to give a different name.
> This can be used like this:
>
> suffix=-bugN
> prefix=/opx/xen/staging${suffix}
> ./configure --prefix=${prefix}
> make rpmball XEN_RPMPKG_SUFFIX=${suffix} \
>      BOOT_DIR=${prefix}/boot \
>      CONFIG_DIR=${prefix}/etc \
>      INITD_DIR=${prefix}/etc/init.d
>
> The result will be "xen-bugN.rpm" instead of "xen.rpm". The benefit is that
> many xen${suffix}.rpm packages can be installed at the same time.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>

This sounds useful, but would it make more sense to name it 
"XEN_PKG_SUFFIX" (i.e., not specify RPM)?  That way some motivated 
person (not necessarily you) could add the same functionality to the 
mkdeb script.

  -George

  reply	other threads:[~2014-07-30 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 10:19 [PATCH] tools/mkrpm: allow custom rpm package name Olaf Hering
2014-07-30 13:08 ` George Dunlap [this message]
2014-07-30 13:21   ` Olaf Hering
2014-07-30 13:42   ` Ian Campbell
2014-07-30 14:06     ` Olaf Hering
2014-07-30 15:02       ` George Dunlap
2014-07-30 15:34         ` Olaf Hering

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=53D8EE46.9040400@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=stefano.stabellini@eu.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).