[meta-ruby] proposal: moving ruby to oe-core

[meta-ruby] proposal: moving ruby to oe-core

[Alexander Kanavin]

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?

Regards,
Alexander

Re: [meta-ruby] proposal: moving ruby to oe-core

[akuster808]

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

Re: [meta-ruby] proposal: moving ruby to oe-core

[Burton, Ross]

On 19 May 2015 at 21:09, akuster808 <akuster808@gmail.com> wrote:

> 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.
>

Agreed, meta-ruby should continue to exist for anything outside of the core
Ruby runtime, exactly like meta-python and meta-cpan.

Ross

Re: [meta-ruby] proposal: moving ruby to oe-core

[Alexander Kanavin]

On 05/20/2015 12:18 PM, Burton, Ross wrote:
>
>> 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.
>>
> Agreed, meta-ruby should continue to exist for anything outside of the core
> Ruby runtime, exactly like meta-python and meta-cpan.
>
>


Alright then. I'll add the ruby runtime to oe-core and won't touch the 
rest. When it appears in master, meta-ruby should be updated to remove 
the recipe.


Alex

Re: [meta-ruby] proposal: moving ruby to oe-core

[akuster808]

Alex,

On 05/20/2015 08:27 AM, Alexander Kanavin wrote:
> On 05/20/2015 12:18 PM, Burton, Ross wrote:
>>
>>> 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.
>>>
>> Agreed, meta-ruby should continue to exist for anything outside of the
>> core
>> Ruby runtime, exactly like meta-python and meta-cpan.
>>
>>
>
>
> Alright then. I'll add the ruby runtime to oe-core and won't touch the
> rest. When it appears in master, meta-ruby should be updated to remove
> the recipe.

I have some ruby class changes but I will wait for this transition to 
complete.

thanks,
Armin

> Alex

Re: [meta-ruby] proposal: moving ruby to oe-core

[Alexander Kanavin]

On 05/20/2015 08:18 PM, akuster808 wrote:
> I have some ruby class changes but I will wait for this transition to 
> complete.

I didn't copy the class to oe-core, because it's not needed for building 
webkit. I copied only the recipe for the ruby runtime. Is that ok?

Alex

Re: [meta-ruby] proposal: moving ruby to oe-core

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]


> On May 20, 2015, at 2:18 AM, Burton, Ross <ross.burton@intel.com> wrote:
> 
> On 19 May 2015 at 21:09, akuster808 <akuster808@gmail.com> wrote:
> 
>> 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.
>> 
> 
> Agreed, meta-ruby should continue to exist for anything outside of the core
> Ruby runtime, exactly like meta-python and meta-cpan.

+1 here as well. We should however make any changes needed in OE-Core to make ruby consumption
easier.



[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]