From: Stefano Babic <sbabic@denx.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Added recipe for libconfig
Date: Thu, 14 Jun 2012 10:00:43 +0200 [thread overview]
Message-ID: <4FD99A2B.2060006@denx.de> (raw)
In-Reply-To: <CAJTo0LbKGqM=pCovegAmZgTz-Q2cKZmZU7qUbYm21KRquydzog@mail.gmail.com>
On 13/06/2012 16:24, Burton, Ross wrote:
> On 13 June 2012 15:22, Stefano Babic <sbabic@denx.de> wrote:
>> no, there is not yet. I add the libconfig to my image and my apllication
>> make use of it. However, I see it as a general purpose library, that one
>> can decide to add or not to the own rootfs.
>>
>> Is there some constraints in OE requiring that a lib can be merged only
>> if a provided package make use of it ?
>
> Surely meta-oe would be a better place for this then?
Understood. Or maybe under meta-yocto/recipes-core ? I will prefer this
one because meta-oe is not part of the yocto distribution. Am I right to
post patches here or am I completely off-topic ?
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2012-06-14 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 13:19 [PATCH] Added recipe for libconfig Stefano Babic
2012-06-13 13:34 ` Otavio Salvador
2012-06-13 14:02 ` Burton, Ross
2012-06-13 14:22 ` Stefano Babic
2012-06-13 14:24 ` Burton, Ross
2012-06-14 8:00 ` Stefano Babic [this message]
2012-06-14 12:58 ` Philip Balister
2012-06-14 14:27 ` Stefano Babic
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=4FD99A2B.2060006@denx.de \
--to=sbabic@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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