From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: [PATCH] tools/mkrpm: allow custom rpm package name
Date: Wed, 30 Jul 2014 16:02:19 +0100
Message-ID: <53D908FB.9030200@eu.citrix.com>
References: <1406542747-9732-1-git-send-email-olaf@aepfle.de>
	<53D8EE46.9040400@eu.citrix.com>
	<1406727739.10402.21.camel@kazak.uk.xensource.com>
	<20140730140626.GA17117@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20140730140626.GA17117@aepfle.de>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Olaf Hering <olaf@aepfle.de>, Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On 07/30/2014 03:06 PM, Olaf Hering wrote:
> On Wed, Jul 30, Ian Campbell wrote:
>
>> I thought RPM allowed multiple packages with the same name (but
>> different versions) to be installed at the same time already. e.g. the
>> kernel packages on such systems are just "kernel", in contrast with
>> Debian which encodes the uname-r into the package name to allow
>> coinstallation.
>>
>> Am I misremembering?
>
> Sure. Its very cumbersome to update a single such xen.rpm. And,
> depending on the branch, they will be all named xen-4.5-0.rpm. After a
> 'zypper patch' installs a security update for Xen my private xen.rpm
> packages will be all gone.
>
> I have a quick look at mkdeb, it looks like the same change could be
> applied there. But I dont run Debian so its hard to tell if that
> approach would work as expected.

So my recent "make src-tarball" patches I had two build targets: one 
where it would make a tarball with a "release-like" name based on "make 
-C xen version" (e.g., xen-4.4.1.tar.gz), and another where it would 
make a tarball with a "developer-like" version based on "git describe". 
  You might think about adding an option like that to the rpm / deb make 
targets as well, so you don't have to invent your own name / remember 
what changeset a particular rpm is based on.

  -George