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

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-07-30 at 14:08 +0100, George Dunlap wrote:
> On 07/28/2014 11:19 AM, Olaf Hering wrote:
> > Even if xen is configured and compiled with different --prefix= so that
> > it operates entirely below $prefix, the resulting package from 'make
> > rpmball' is always called "xen.rpm".
> >
> > Use an environment name to give a different name.
> > This can be used like this:
> >
> > suffix=-bugN
> > prefix=/opx/xen/staging${suffix}
> > ./configure --prefix=${prefix}
> > make rpmball XEN_RPMPKG_SUFFIX=${suffix} \
> >      BOOT_DIR=${prefix}/boot \
> >      CONFIG_DIR=${prefix}/etc \
> >      INITD_DIR=${prefix}/etc/init.d
> >
> > The result will be "xen-bugN.rpm" instead of "xen.rpm". The benefit is that
> > many xen${suffix}.rpm packages can be installed at the same time.

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?

> >
> > Signed-off-by: Olaf Hering <olaf@xxxxxxxxx>
> 
> This sounds useful, but would it make more sense to name it 
> "XEN_PKG_SUFFIX" (i.e., not specify RPM)?  That way some motivated 
> person (not necessarily you) could add the same functionality to the 
> mkdeb script.
> 
>   -George
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel