From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/mkrpm: allow custom rpm package name
Date: Wed, 30 Jul 2014 16:06:26 +0200 [thread overview]
Message-ID: <20140730140626.GA17117@aepfle.de> (raw)
In-Reply-To: <1406727739.10402.21.camel@kazak.uk.xensource.com>
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.
diff --git a/tools/misc/mkdeb b/tools/misc/mkdeb
index 3bbf881..db7a003 100644
--- a/tools/misc/mkdeb
+++ b/tools/misc/mkdeb
@@ -33,8 +33,8 @@ fi
# Fill in the debian boilerplate
mkdir -p deb/DEBIAN
cat >deb/DEBIAN/control <<EOF
-Package: xen-upstream
-Source: xen-upstream
+Package: xen-upstream$XEN_PKG_SUFFIX
+Source: xen-upstream$XEN_PKG_SUFFIX
Version: $version
Architecture: $arch
Maintainer: Unmaintained snapshot
Olaf
next prev parent reply other threads:[~2014-07-30 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 10:19 [PATCH] tools/mkrpm: allow custom rpm package name Olaf Hering
2014-07-30 13:08 ` George Dunlap
2014-07-30 13:21 ` Olaf Hering
2014-07-30 13:42 ` Ian Campbell
2014-07-30 14:06 ` Olaf Hering [this message]
2014-07-30 15:02 ` George Dunlap
2014-07-30 15:34 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140730140626.GA17117@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.