From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 2/2] ruby: Add ruby 1.9.3 recipe
Date: Thu, 28 Jun 2012 10:08:41 -0700 [thread overview]
Message-ID: <4FEC8F99.9080100@linux.intel.com> (raw)
In-Reply-To: <10317249.W4Cacltz0J@helios>
On 06/28/2012 09:24 AM, Paul Eggleton wrote:
> On Thursday 28 June 2012 18:02:47 Koen Kooi wrote:
>> Op 28 jun. 2012, om 11:47 heeft<jackie.huang@windriver.com>
> <jackie.huang@windriver.com> het volgende geschreven:
>>> From: Jackie Huang<jackie.huang@windriver.com>
>>>
>>> Took ruby 1.8.7 from OE and updated to 1.9.3-p194.
>>> Most of the 1.9.3 patches originate from ruby-1.9.3.194-10.1.fc17.src.rpm
>>
>> Is ruby something that belongs into oe-core?
>
> I was thinking the same thing - it's not something that everyone needs, so
> really it doesn't belong there IMHO.
>
> Where it should go is another question. If we would expect to add lots of
> supplementary ruby recipes in future then perhaps its own layer would be
> appropriate; otherwise I guess it can go into meta-oe.
>
Agreed, oe-core is not the right place, meta-oe would be right place to
start, it is upgrading a recipe from OE-Classic.
Sau!
> Cheers,
> Paul
>
next prev parent reply other threads:[~2012-06-28 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 9:47 [PATCH 1/2] ruby: Add yaml for ruby jackie.huang
2012-06-28 9:47 ` [PATCH 2/2] ruby: Add ruby 1.9.3 recipe jackie.huang
2012-06-28 16:02 ` Koen Kooi
2012-06-28 16:24 ` Paul Eggleton
2012-06-28 17:08 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-28 8:14 [PATCH 1/2] ruby: Add yaml for ruby jackie.huang
2012-06-28 8:14 ` [PATCH 2/2] ruby: Add ruby 1.9.3 recipe jackie.huang
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=4FEC8F99.9080100@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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 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.