Re: [PATCH] tools/mkrpm: allow custom rpm package name

[George Dunlap <george.dunlap@eu.citrix.com>]

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