From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: CONFLICTS as keyword or just misspelled RCONFLICTS?
Date: Tue, 8 May 2012 14:20:16 -0500 [thread overview]
Message-ID: <4FA971F0.8020406@windriver.com> (raw)
In-Reply-To: <20120508180256.GB3138@jama.jama.net>
On 5/8/12 1:02 PM, Martin Jansa wrote:
> It's used in few recipes (lately used in kmod recipe), but no .bbclass and no match in bitbake
>
> OE @ ~/openembedded-core $ git grep CONFLICTS | grep -v RCONFLICTS | grep -v TUNE_CONFLICTS | grep -v TUNECONFLICTS
> meta/recipes-connectivity/openssh/openssh_6.0p1.bb:CONFLICTS_${PN} = "dropbear"
> meta/recipes-core/gettext/gettext_0.18.1.1.bb:CONFLICTS_${PN} = "proxy-libintl"
> meta/recipes-graphics/xorg-proto/compositeproto_0.4.2.bb:CONFLICTS = "compositeext"
> meta/recipes-graphics/xorg-proto/damageproto_1.2.1.bb:CONFLICTS = "damageext"
> meta/recipes-graphics/xorg-proto/fixesproto_5.0.bb:CONFLICTS = "fixesext"
> meta/recipes-graphics/xorg-proto/randrproto_1.3.2.bb:CONFLICTS = "randrext"
> meta/recipes-graphics/xorg-proto/recordproto_1.14.1.bb:CONFLICTS = "recordext"
> meta/recipes-graphics/xorg-proto/renderproto_0.11.1.bb:CONFLICTS = "renderext"
> meta/recipes-graphics/xorg-proto/resourceproto_1.2.0.bb:CONFLICTS = "resourceext"
> meta/recipes-graphics/xorg-proto/xf86dgaproto_2.1.bb:CONFLICTS = "xxf86dgaext"
> meta/recipes-graphics/xorg-proto/xf86vidmodeproto_2.3.1.bb:CONFLICTS = "xxf86vmext"
> meta/recipes-sato/matchbox-desktop-sato/matchbox-desktop-sato_git.bb:CONFLICTS = "matchbox-common"
> meta/recipes-support/db/db_5.1.19.bb:CONFLICTS = "db3"
Not finding CONFLICTS defined anywhere, including bitbake -- I'm inclined to
agree that these should have been RCONFLICTS_<pn>, and weren't.
> BTW: IIRC TUNE_CONFLICTS/TUNECONFLICTS inconsistency was discussed on ML already
> (I could not find that thread, but still it's used in meta/conf/machine/include/arm
Ya, patches to fix these, and actually check them were sent to the list, but I
don't believe they have been merged yet.
--Mark
> Cheers,
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-05-08 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 18:02 CONFLICTS as keyword or just misspelled RCONFLICTS? Martin Jansa
2012-05-08 19:20 ` Mark Hatle [this message]
2012-05-08 19:25 ` Peter Seebach
2012-06-16 6:51 ` Martin Jansa
2012-07-07 8:31 ` [PATCH] conf/machine: replace TUNE_CONFLICTS with TUNECONFLICTS Martin Jansa
2012-07-17 15:09 ` Saul Wold
2012-06-16 18:08 ` [PATCH 1/2] recipes: replace CONFLICTS with RCONFLICTS_${PN} Martin Jansa
2012-06-16 18:08 ` [PATCH 2/2] tzdata, matchbox-session, mini-x-session: replace RCONFLICTS with RCONFLICTS_ Martin Jansa
2012-06-18 12:42 ` [PATCH 1/2] recipes: replace CONFLICTS with RCONFLICTS_${PN} Richard Purdie
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=4FA971F0.8020406@windriver.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.