From: Mark Hatle <mark.hatle@windriver.com>
To: Leah <leah@wolfssl.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: Add recipe to openembedded, adjust layer
Date: Wed, 30 Jul 2014 13:09:53 -0500 [thread overview]
Message-ID: <53D934F1.2030807@windriver.com> (raw)
In-Reply-To: <CAL0pqZ2VaH_mCrNkXQvUOWNC_eWSTUUk-Gyp1eX06XL17EvLQA@mail.gmail.com>
On 7/30/14, 12:53 PM, Leah wrote:
> Hi,
>
> I have a recipe - cyassl_3.1.0.bb <http://cyassl_3.1.0.bb>, a lightweight ssl
> library that I would like to add to openembedded. I am not sure as to the best
> location, perhaps recipes-connectivity? Do I need to submit this recipe the same
> way I would submit a layer?
Usually we say meta-oe first -- unless the item shows a significant reason to be
in oe-core. (The gating factor for oe-core is it really does need to be a core
piece of functionality, and something the maintainers are willing to promise to
fix if it brakes. Due to limited resources, it's currently difficult for any of
the maintainers to promise that.. thus meta-oe first.)
> Also, is there a way to edit my current layer's information(meta-wolfssl) on the
> openembedded layer index?
A number of us have access to edit the layer information (myself included).
Feel free to send me an email with the edits.
--Mark
> Thanks,
>
> Leah
>
> --
>
> Leah Thompson
> www.wolfssl.com <http://www.wolfssl.com>
> leah@wolfssl.com <mailto:leah@wolfssl.com>
> 406-570-1389 <tel:406-570-1389>
> Skype: lchristina26
>
>
>
>
>
> --
>
> Leah Thompson
> www.wolfssl.com <http://www.wolfssl.com>
> leah@wolfssl.com <mailto:leah@wolfssl.com>
> 406-570-1389
> Skype: lchristina26
>
>
>
>
next prev parent reply other threads:[~2014-07-30 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL0pqZ0w0qmwPUhtEOfc6DCMggH6t_ELWOxhpWPSCxETta-u9A@mail.gmail.com>
2014-07-30 17:53 ` Add recipe to openembedded, adjust layer Leah
2014-07-30 18:07 ` Saul Wold
2014-07-30 18:09 ` Mark Hatle [this message]
2014-07-31 9:05 ` Paul Eggleton
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=53D934F1.2030807@windriver.com \
--to=mark.hatle@windriver.com \
--cc=leah@wolfssl.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