From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 1/5] tools/mkrpm: improve version.release handling Date: Mon, 23 Mar 2015 18:05:04 +0100 Message-ID: <20150323170503.GA12484@aepfle.de> References: <1426872279-5001-1-git-send-email-olaf@aepfle.de> <1426872279-5001-2-git-send-email-olaf@aepfle.de> <55103C3E.3000302@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <55103C3E.3000302@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Wei Liu , Stefano Stabellini , Ian Jackson , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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)" make rpmball This may work as well for me. mkrpm handles PKG_SUFFIX already. So PKG_RELEASE or RPM_RELEASE would be a suitable variable name. I will try this suggestion. Olaf