All of lore.kernel.org
 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: Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2] tools/mkrpm: improve version.release handling
Date: Wed, 25 Mar 2015 14:01:43 +0000	[thread overview]
Message-ID: <5512BFC7.4010403@eu.citrix.com> (raw)
In-Reply-To: <1427207862-28204-1-git-send-email-olaf@aepfle.de>

On 03/24/2015 02:37 PM, Olaf Hering wrote:
> An increasing version and/or release number helps to update existing
> packages without --force as in "rpm Uvh --force xen.rpm". Instead its
> possible to do "rpm -Fvh *.rpm" to update only already installed
> packages.
> 
> The usage of --force disables essentials checks such as file conflict
> detection. As a result the new xen.rpm may overwrite files owned by
> other packages.
> 
> With the current way of calculating version-release it is difficult to
> get an increasing release number into the spec file. The release is
> always zero unless "make make XEN_VENDORVERSION=`date +.%s`" is used,
> which has the bad side effect that xen.gz always gets a different
> filename every time.
> 
> Update mkrpm to recognize PKG_RELEASE=. Its value will be appended to
> the Release string. It can be filled with a time stamp, like:
>  make rpmball PKG_RELEASE="`date +%Y%m%d%H%M%S`"
> 
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
> Cc: George Dunlap <george.dunlap@eu.citrix.com>
> ---
>  INSTALL          | 4 +++-
>  tools/misc/mkrpm | 4 +---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/INSTALL b/INSTALL
> index 1b67c36..8735bf5 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -197,8 +197,10 @@ BOOT_DIR=
>  EFI_DIR=
>  
>  The make target 'rpmball' will build a xen.rpm. This variable can be
> -used to append a custom string to the name.
> +used to append a custom string to the name. In addition a string can be
> +appended to the rpm Release: tag.
>  PKG_SUFFIX=
> +PKG_RELEASE=
>  
>  The hypervisor will report a certain version string. This variable can
>  be used to append a custom string to the version.
> diff --git a/tools/misc/mkrpm b/tools/misc/mkrpm
> index 9b8c6d9..f9363a1 100644
> --- a/tools/misc/mkrpm
> +++ b/tools/misc/mkrpm
> @@ -17,9 +17,7 @@ xenroot="$1"
>  # version and release.  Default to "0" if there isn't a release.
>  v=(${2/-/ })
>  version=${v[0]}
> -release=${v[1]}
> -
> -[[ -n "$release" ]] || release="0"
> +release="${v[1]:-0}${PKG_RELEASE:+.$PKG_RELEASE}"

Thanks Olaf.  I kicked the tires a bit and it seems to work as described.

I think in my ideal world the result would look like this:

case  ${v[1]} &&  PKG_RELEASE: "${v[1]}.${PKG_RELEASE}"
case  ${v[1]} && !PKG_RELEASE: "${v[1]}"
case !${v[1]} &&  PKG_RELEASE: "${PKG_RELEASE}"
case !${v[1]} && !PKG_RELEASE: "0"

Right now the 3rd case looks like "0.${PKG_RELEASE}".  But I think
you've put up enough with my pickiness.  :-)

I may come back and see if I can make a patch so it acts like above; but
for now:

Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
Tested-by: George Dunlap <george.dunlap@eu.citrix.com>

  reply	other threads:[~2015-03-25 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 14:37 [PATCH v2] tools/mkrpm: improve version.release handling Olaf Hering
2015-03-25 14:01 ` George Dunlap [this message]
2015-03-26  7:39   ` Olaf Hering
2015-03-30  9:08   ` Ian Campbell

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=5512BFC7.4010403@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=wei.liu2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.