From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] Add a "make rpmball" target
Date: Mon, 3 Mar 2014 18:31:50 +0100 [thread overview]
Message-ID: <20140303173150.GB26596@aepfle.de> (raw)
In-Reply-To: <5314AF8A.2070301@eu.citrix.com>
On Mon, Mar 03, George Dunlap wrote:
> "remove another named package(s) when this package is installed" -- I think
> that's a bit more than we want in the rpmball. I'd much rather the
> developer have to remove the conflicting packages themselves, rather than
> have it done automatically.
It would mean "rpm -e --nodeps xen-tools xen-libs" has to be used. If
any other package depends on the xen-libs for example, then in my
opinion its better to get a clear "libxl.so.4 is required by XY" when
doing "rpm -U xen.rpm".
Olaf
next prev parent reply other threads:[~2014-03-03 17:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:59 [PATCH] Add a "make rpmball" target George Dunlap
2014-03-03 16:07 ` George Dunlap
2014-03-03 22:34 ` Don Slutz
2014-03-03 23:08 ` Don Slutz
2014-03-03 23:37 ` M A Young
2014-03-03 23:46 ` Don Slutz
2014-03-03 23:52 ` M A Young
2014-03-04 10:26 ` George Dunlap
2014-03-03 16:23 ` Olaf Hering
2014-03-03 16:34 ` George Dunlap
2014-03-03 16:36 ` George Dunlap
2014-03-03 17:31 ` Olaf Hering [this message]
2014-03-03 17:23 ` Olaf Hering
2014-03-03 17:27 ` Dario Faggioli
2014-03-03 17:30 ` George Dunlap
2014-03-03 17:59 ` Ian Jackson
2014-03-03 22:53 ` Dario Faggioli
2014-03-03 23:11 ` Olaf Hering
2014-03-04 12:19 ` Ian Jackson
2014-03-03 18:19 ` Ian Campbell
2014-03-03 23:06 ` Olaf Hering
2014-03-03 20:51 ` Don Slutz
2014-03-04 11:41 ` George Dunlap
2014-03-03 22:52 ` Dario Faggioli
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=20140303173150.GB26596@aepfle.de \
--to=olaf@aepfle.de \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).