From: akuster808 <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-ruby] proposal: moving ruby to oe-core
Date: Tue, 19 May 2015 13:09:22 -0700 [thread overview]
Message-ID: <555B9872.50301@gmail.com> (raw)
In-Reply-To: <555B59D4.80304@linux.intel.com>
On 05/19/2015 08:42 AM, Alexander Kanavin wrote:
> Hello meta-ruby maintainers,
>
> I am trying to update webkit-gtk in oe-core to latest upstream version
> (it's fallen badly out of date), and that requires having ruby during
> build time. So I would like to propose that ruby recipes are moved to
> oe-core, and you keep maintaining them there. How does it sound to you?
I don't have an issue with that. Do you need both Ruby and bundler? I
believe there is value in having additional ruby packages outside core,
like python is structured.
I think it might be more of issue for OE-core folks.
My concern is core is getting bloated.
regards and thanks for asking.
Armin
>
> Regards,
> Alexander
next prev parent reply other threads:[~2015-05-19 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 15:42 [meta-ruby] proposal: moving ruby to oe-core Alexander Kanavin
2015-05-19 20:09 ` akuster808 [this message]
2015-05-20 9:18 ` Burton, Ross
2015-05-20 15:27 ` Alexander Kanavin
2015-05-20 17:18 ` akuster808
2015-05-21 12:56 ` Alexander Kanavin
2015-05-20 19:10 ` 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=555B9872.50301@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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.