Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-24 Thread Olaf Hering
On Mon, Mar 23, George Dunlap wrote: > On 03/23/2015 06:49 PM, Olaf Hering wrote: > > release will be anything after a dash, or 0. And an optional ".$PKG_RELEASE" > > will be appended. > Just trying to decode this: So if I were using PKG_RELEASE=$(date ...), > then I'd get something like > > xen-

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread George Dunlap
On 03/23/2015 06:49 PM, Olaf Hering wrote: > On Mon, Mar 23, George Dunlap wrote: > >> On Mon, Mar 23, 2015 at 5:52 PM, Olaf Hering wrote: >>> On Mon, Mar 23, George Dunlap wrote: xen-4.6_unstable-20150323160547.x86_64.rpm >>> Do you want to continue to get "unstable" as release? >>> My patc

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread Olaf Hering
On Mon, Mar 23, George Dunlap wrote: > On Mon, Mar 23, 2015 at 5:52 PM, Olaf Hering wrote: > > On Mon, Mar 23, George Dunlap wrote: > >> xen-4.6_unstable-20150323160547.x86_64.rpm > > Do you want to continue to get "unstable" as release? > > My patch uses everything passed as "$2" as Version stri

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread George Dunlap
On Mon, Mar 23, 2015 at 5:52 PM, Olaf Hering wrote: > On Mon, Mar 23, George Dunlap wrote: > >> xen-4.6_unstable-20150323160547.x86_64.rpm > > Do you want to continue to get "unstable" as release? > My patch uses everything passed as "$2" as Version string. I think thats > ok. I think "unstable"

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread Olaf Hering
On Mon, Mar 23, George Dunlap wrote: > xen-4.6_unstable-20150323160547.x86_64.rpm Do you want to continue to get "unstable" as release? My patch uses everything passed as "$2" as Version string. I think thats ok. Release will be either 0 or $PKG_DATE. Olaf _

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread Olaf Hering
On Mon, Mar 23, George Dunlap wrote: > I'm not really happy with having the massive number show up > automatically when anyone makes an rpm. What would you think about > adding a variable where you could set this as part of the build process? > e.g., > XEN_RPM_RELEASE="$(date +%Y%m%d%H%M%S)" m

Re: [Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-23 Thread George Dunlap
On 03/20/2015 05:24 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

[Xen-devel] [PATCH 1/5] tools/mkrpm: improve version.release handling

2015-03-20 Thread Olaf Hering
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