Openembedded Core Discussions
 help / color / mirror / Atom feed
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:03:22 +0100	[thread overview]
Message-ID: <1347660202.4444.10.camel@x121e.pbcl.net> (raw)
In-Reply-To: <5053A818.4070402@windriver.com>

On Fri, 2012-09-14 at 16:56 -0500, Mark Hatle wrote:
> On 9/14/12 4:50 PM, Phil Blundell wrote:
> > On Fri, 2012-09-14 at 18:29 +0100, Paul Eggleton wrote:
> >> Unfortunately with rpm at least, this results in xserver-xorg-module-exa
> >> being installed in preference to xserver-xorg when constructing the root
> >> filesystem, which is clearly not desirable.
> >
> > Surely this is a bug in the rpm packaging backend and ought to be fixed
> > there.
> 
> If a package "replaces" another, it has priority.  What is the desired behavior 
> in this case?

The conventional behaviour has been that:

- if a package RREPLACES another (without declaring any other
dependencies) then it is allowed to overwrite files in that package
without producing an error.  This is necessary when files move from one
package to another but both should remain installed.

- if a package wishes to entirely replace another one, it should both
RREPLACE and RCONFLICT with the old one in order to force it off.
Generally it would also want to RPROVIDE that package otherwise the
replacement is liable to cause broken dependencies.

p.




  reply	other threads:[~2012-09-14 22:18 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 [this message]
2012-09-14 22:13       ` Mark Hatle
2012-09-14 22:16         ` Phil Blundell
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=1347660202.4444.10.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