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:37:38 +0100 [thread overview]
Message-ID: <1347662258.4444.34.camel@x121e.pbcl.net> (raw)
In-Reply-To: <5053AFAB.6000409@windriver.com>
On Fri, 2012-09-14 at 17:28 -0500, Mark Hatle wrote:
> Based on that, I'm not sure what RREPLACES is being used for:
>
> FILES_${PN} = "${bindir} ${libdir}/X11/Options ${libdir}/X11/Cards
> ${libdir}/X11/getconfig ${libdir}/X11/etc ${libdir}/modules/*.so
> ${libdir}/xorg/modules/*.so /etc/X11 ${libdir}/xorg/protocol.txt
> ${datadir}/X11/xorg.conf.d"
>
> Since under the packaging rules, that one file will only exist in the one
> package, and it won't ever exist in both packages.
>
> So Replaces is wrong under either definition from what I can tell.
The point is that it was in older versions of xserver-xorg. It's indeed
not in the current version, and in fact it can't be since (due to the
way that FILES works) there is no way for a single file to end up in
more than one of the PACKAGES for a given recipe.
In the particular case at hand I think the problem is relatively minor,
since folks who have an old xserver-xorg installed can upgrade by first
installing the new xserver-xorg (which doesn't ship libexa.so) and then
installing xserver-xorg-module-exa. But, if the new xserver-xorg had
depended on xserver-xorg-module-exa then this wouldn't have worked
without the RREPLACES.
p.
next prev parent reply other threads:[~2012-09-14 22:52 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
2012-09-14 22:28 ` Mark Hatle
2012-09-14 22:37 ` Phil Blundell [this message]
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=1347662258.4444.34.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