From: Phil Blundell <philb@gnu.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] xserver-xorg: remove broken RREPLACES
Date: Fri, 14 Sep 2012 23:16:05 +0100 [thread overview]
Message-ID: <1347660965.4444.17.camel@x121e.pbcl.net> (raw)
In-Reply-To: <5053ABF3.8010708@windriver.com>
On Fri, 2012-09-14 at 17:13 -0500, Mark Hatle wrote:
> Coming from the RPM world, that behavior is entirely unexpected. There is no
> way (by design) for an RPM package to be tagged as being allowed to replace
> files of another package.
How would rpm conventionally deal with the situation at hand here (a
file which was previously in xserver-xorg and is now in
xserver-xorg-module-exa)?
p.
next prev parent reply other threads:[~2012-09-14 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 17:29 [PATCH] xserver-xorg: remove broken RREPLACES Paul Eggleton
2012-09-14 21:50 ` Phil Blundell
2012-09-14 21:56 ` Mark Hatle
2012-09-14 22:03 ` Phil Blundell
2012-09-14 22:13 ` Mark Hatle
2012-09-14 22:16 ` Phil Blundell [this message]
2012-09-14 22:28 ` Mark Hatle
2012-09-14 22:37 ` Phil Blundell
2012-09-14 22:45 ` Mark Hatle
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=1347660965.4444.17.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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