Openembedded Core Discussions
 help / color / mirror / Atom feed
From: jhuang0 <jackie.huang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] ruby: Add from OE-Classic and update to 1.9.3-p194
Date: Wed, 10 Oct 2012 09:46:48 +0800	[thread overview]
Message-ID: <5074D388.6060008@windriver.com> (raw)
In-Reply-To: <CAJTo0LY9xi7=s0N1LX_zc9Hk3L1Wb15JRF4nN5sar8anjepJKA@mail.gmail.com>



On 10/9/2012 8:38 PM, Burton, Ross wrote:
> On 9 October 2012 11:38, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>>> * I sent this months ago but was told that oe-core is not the right place,
>>>    however, we think it makes sense to add ruby to complete the scripting
>>>    language set of: python, perl, ruby, so I re-send it.
>>
>> I have to say, my opinion is the same now as it was then. Ruby support is
>> certainly useful to have, and we have had requests for it; but unlike Perl and
>> Python which are needed by many other things, nothing we have in OE-Core
>> actually needs Ruby; thus it really belongs in another layer IMHO.
>
> Agreed.  If we're completing the set of scripting languages there's
> plenty left out.  A standalone meta-ruby layer that contains the
> runtime and pretty much every useful library sounds like a much better
> idea as the runtime and the libraries will be in a single place and
> incompatible changes can be done in a single move without having to
> co-ordinate multiple layers.

I see, thanks, so I think I should send it to meta-oe at this point.

Thanks,
Jackie

>
> Ross
>

-- 
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745



  reply	other threads:[~2012-10-10  2:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  6:36 [PATCH 0/4] ruby: Add from OE-Classic and update to 1.9.3-p194 jackie.huang
2012-10-09  6:36 ` [PATCH 1/4] libyaml: Add recipe from meta-oe jackie.huang
2012-10-09  6:36 ` [PATCH 2/4] libyaml: update to 0.1.4 jackie.huang
2012-10-09  6:36 ` [PATCH 3/4] ruby: Add from OE-Classic jackie.huang
2012-10-09  6:36 ` [PATCH 4/4] ruby: update to 1.9.3-194 jackie.huang
2012-10-09 10:38 ` [PATCH 0/4] ruby: Add from OE-Classic and update to 1.9.3-p194 Paul Eggleton
2012-10-09 12:38   ` Burton, Ross
2012-10-10  1:46     ` jhuang0 [this message]
2012-10-09 17:07   ` Khem Raj

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=5074D388.6060008@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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