From: Bob Cochran <openembedded@mindchasers.com>
To: openembedded-devel@lists.openembedded.org
Subject: finding mime-support in multiple oe trees?
Date: Fri, 11 May 2012 08:45:50 -0400 [thread overview]
Message-ID: <4FAD09FE.4040101@mindchasers.com> (raw)
Hello,
I can find recipes for mime-support in both meta-openembedded and
meta-openembedded-contrib under meta-oe/recipes-support. The former has
a 3.48 recipe and the latter has a 3.44 recipe.
Is finding the same recipe in multiple trees (not including classic) a
glitch or the norm?
I'm going on the assumption that a production image is best off pulling
a recipe from a non contrib layer (when available) unless the contrib
layer / recipe solves a specific need.
Thanks in advance for providing any insight into this issue of multiple
recipes in different trees.
Bob
next reply other threads:[~2012-05-11 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 12:45 Bob Cochran [this message]
2012-05-11 13:36 ` finding mime-support in multiple oe trees? Paul Eggleton
2012-05-11 13:37 ` Martin Jansa
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=4FAD09FE.4040101@mindchasers.com \
--to=openembedded@mindchasers.com \
--cc=openembedded-devel@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