[OE-core] Feedback on building openembedded-core for qemuarm. Excerpts from buildlog

[Frans Meulenbroeks]

2011/12/1 Ulf Samuelsson <openembedded-core at emagii.com>

>  2011-12-01 16:37, Koen Kooi skrev:
>
> Op 1 dec. 2011, om 14:16 heeft Philip Balister het volgende geschreven:
>
>
>  On 11/29/2011 03:06 PM, Koen Kooi wrote:
>
>  Op 29 nov. 2011, om 20:36 heeft Ulf Samuelsson het volgende geschreven:
>
>
>  On 2011-11-29 16:03, Richard Purdie wrote:
>
>   2.    "ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz" <ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz> is no longer
> available.
>         tzdata , same problem.
>         The recipe is located in two places.
>         meta-openembedded/meta-oe/recipes-extended/tz*/tz*.bb have the
> problem
>         This is what the build uses.
>
>  This is something to raise with the meta-oe maintainers. I think there
> isn't a problem in OECore.
>
>  Since we now have a large number of layers, maybe it is a good
> idea to define in each layer,  how the "git send email" should behave in
> by providing a better ".git/config" file in the trunk?
>
>
> I.E:
>
> [sendemail]
>   to = openembedded-core at lists.openembedded.org
>
> or
> meta-angstrom/.git/config
> [sendemail]
>   to = angstrom-distro-devel at linuxtogo.org
> [format]
>   subjectprefix = "[meta-angstrom]"
>
>
> No need to look in the README file with this.
>
>  That assumes git-send-email is the preferred way, which it isn;'t for a lot of layers
>
>  Even if it is not the preferred way, it would direct the discussion to
> the appropriate list. This would reduce the number of mis-directed
> emails to this list.
>
>  You can't fix stupid, sadly.
>
>
> Tend to disagree.
> The whole purpose of OE is to make it possible for people,
> stupid or not, to go off and make things which they would
> not be able to do on their own.
>
> As I see it, it is no real drawback of adding this, and at least some
> benefit.
>
> As for not beeing the preferred way, I think that people that engage
> themselves
> in a layer should adopt the preferred way.
>
> Anyone seeing a bad layer, applicable only to a small subset of users,
> interfering with their build should not be expected
> to put a lof of effort into the fix, except reporting it.
> Then the mailing list is probably the easiest thing to use.
>
> If this is not there, expect them to send it to the official list.
> BR
> Ulf
>

My two cents:
If I see a small problem in a layer that I am not working on and submitting
a patch is easy (e.g. committing the patch, doing a send-email) I would
probably do so.
If it becomes harder (since I have to find what list it needs to be send
to) chances that the effort is made become smaller and actually depending
on the time at hand
If i have to set up a git mirror just for this single patch, forget it.

I think if we want to encourage people fixing and submitting patches it
helps to have a mailing address in the config file.
But of course if you prefer to do maintenance only with the happy few, this
is less desirable (but then you should probably consider not accepting
mailed patches at all)

frans
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20111202/6e4e3460/attachment-0002.html>