From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: jackie.huang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] ruby: Add from OE-Classic and update to 1.9.3-p194
Date: Tue, 09 Oct 2012 11:38:32 +0100 [thread overview]
Message-ID: <2072868.bxk9nbbmYZ@helios> (raw)
In-Reply-To: <cover.1349689653.git.jackie.huang@windriver.com>
Hi Jackie,
On Tuesday 09 October 2012 14:36:53 jackie.huang@windriver.com wrote:
> From: Jackie Huang <jackie.huang@windriver.com>
>
> * 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.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-09 10:51 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 ` Paul Eggleton [this message]
2012-10-09 12:38 ` [PATCH 0/4] ruby: Add from OE-Classic and update to 1.9.3-p194 Burton, Ross
2012-10-10 1:46 ` jhuang0
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=2072868.bxk9nbbmYZ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jackie.huang@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 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.