Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: siteinfo for recipes oe-core lacks?
Date: Wed, 13 Jul 2011 20:20:58 -0500	[thread overview]
Message-ID: <4E1E447A.2060703@windriver.com> (raw)
In-Reply-To: <4E1E18AA.2050808@mentor.com>

On 7/13/11 5:14 PM, Tom Rini wrote:
> Hey all,
> 
> Do we have an opinion on siteinfo for recipes that oe-core lacks?  I
> have two easy examples:
> - mono: neither meta-oe nor oe-core have a recipe, we have siteinfo
> stuff specific to it.  Ignore it? drop it?  update it with what meta-oe has?
> - postgresql: meta-oe has it, oe-core lacks it.  Keep in meta-oe only?
> 

For both of them, I'd keep them as local to the recipe as possible.. no recipe,
no siteinfo listed.

--Mark



  reply	other threads:[~2011-07-14  1:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 22:14 siteinfo for recipes oe-core lacks? Tom Rini
2011-07-14  1:20 ` Mark Hatle [this message]
2011-07-14  1:44   ` Tom Rini
2011-07-14  2:01     ` Mark Hatle
2011-07-14  2:07       ` Tom Rini
2011-07-14  2:35         ` 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=4E1E447A.2060703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox