From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.pbcl.net ([88.198.119.4] helo=hetzner.pbcl.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1TCeDC-0005kZ-Te for openembedded-core@lists.openembedded.org; Sat, 15 Sep 2012 00:18:10 +0200 Received: from blundell.swaffham-prior.co.uk ([91.216.112.25] helo=[192.168.114.6]) by hetzner.pbcl.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TCe12-0002hh-LA; Sat, 15 Sep 2012 00:05:36 +0200 Message-ID: <1347660202.4444.10.camel@x121e.pbcl.net> From: Phil Blundell To: Mark Hatle Date: Fri, 14 Sep 2012 23:03:22 +0100 In-Reply-To: <5053A818.4070402@windriver.com> References: <1347643776-4028-1-git-send-email-paul.eggleton@linux.intel.com> <1347659456.4444.1.camel@x121e.pbcl.net> <5053A818.4070402@windriver.com> X-Mailer: Evolution 3.4.3-1 Mime-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH] xserver-xorg: remove broken RREPLACES X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 22:18:11 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.