pushing mamona things upstream

pushing mamona things upstream

[Rodrigo Vivi]

Hi guys,

I'm afraid we from Mamona are in debit with OE. It has been passed
long time without sending our things back upstream.

But now that git migration has finished it will be easy to work closer.

My plan is to send directly all patches that change mamona packages,
tasks and configuration. This shouldn't break anyone's build. (Get
prepared for an avalanche of commits :) )

After that it will be easy for us to see what we have different. We'll
put these differences in a table and ask for permission by email or
reporting a bug.

Any concerns?

Cheers,

-- 
Rodrigo Vivi
INdT - Instituto Nokia de Tecnologia
Blog: http://blog.vivi.eng.br
GPG: 0x905BE242 @ wwwkeys.pgp.net

Re: pushing mamona things upstream

[Marcin Juszkiewicz]

Thursday 23 of October 2008 06:59:11 Rodrigo Vivi napisał(a):
> Hi guys,
>
> I'm afraid we from Mamona are in debit with OE. It has been passed
> long time without sending our things back upstream.
>
> But now that git migration has finished it will be easy to work
> closer.
>
> My plan is to send directly all patches that change mamona packages,
> tasks and configuration. This shouldn't break anyone's build. (Get
> prepared for an avalanche of commits :) )

This should fix some builds even - mamona tasks lack deps now iirc.

> After that it will be easy for us to see what we have different.
> We'll put these differences in a table and ask for permission by
> email or reporting a bug.

You can also push to own branch and ask for reviewing it.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://blog.haerwu.biz/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

Re: pushing mamona things upstream

[Denys Dmytriyenko]

On Thu, Oct 23, 2008 at 01:59:11AM -0300, Rodrigo Vivi wrote:
> My plan is to send directly all patches that change mamona packages,
> tasks and configuration.

Thanks for doing it.

> This shouldn't break anyone's build. (Get prepared for an avalanche of 
> commits :) )

At least in theory. But in reality it got broken:

ERROR: Could not include required file ../gcc/gcc3-build.inc while parsing /OE/openembedded/packages/mamona/gcc-noemu_4.1.2.bb

You forgot the gcc/gcc3-build.inc and BitBake chokes on it while parsing the 
tree.

-- 
Denys

Re: pushing mamona things upstream

[Ricardo Salveti]

On Thu, Oct 23, 2008 at 8:16 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> On Thu, Oct 23, 2008 at 01:59:11AM -0300, Rodrigo Vivi wrote:
>> My plan is to send directly all patches that change mamona packages,
>> tasks and configuration.
>
> Thanks for doing it.
>
>> This shouldn't break anyone's build. (Get prepared for an avalanche of
>> commits :) )
>
> At least in theory. But in reality it got broken:
>
> ERROR: Could not include required file ../gcc/gcc3-build.inc while parsing /OE/openembedded/packages/mamona/gcc-noemu_4.1.2.bb
>
> You forgot the gcc/gcc3-build.inc and BitBake chokes on it while parsing the
> tree.

It seems to be fixed at 3a83d1fb3fd0fdbbf763e5f495ef9046f09e15b9

We still have some issues to fix even at our commits, like we had with
this one. We'll first try to push things that shouldn't be very
related with other distros, mostly to avoid breaking every build.

Probably we'll need some kind of Mamona branch at OE for the patches
that needs review, like ones that touch any bbclass.

At the moment we'll try to track what we need to push in a page at our
Trac, but let's see how it goes.

Thanks for the report.

Cheers,
-- 
Ricardo Salveti de Araujo

Re: pushing mamona things upstream

[Michael 'Mickey' Lauer]

Am Friday 24 October 2008 05:40:05 schrieb Ricardo Salveti:
> Probably we'll need some kind of Mamona branch at OE for the patches
> that needs review, like ones that touch any bbclass.

Agreed, please commit to a branch for the things that
a) do not apply cleanly, or
b) touch "core" packages and/or classes.

Thanks,

:M: