From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Cc: Yocto Project <public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org>
Subject: Re: Layer model doomed, unless we all work together
Date: Thu, 20 Nov 2014 14:04:20 +0200 [thread overview]
Message-ID: <546DD8C4.6010800@reliableembeddedsystems.com> (raw)
In-Reply-To: <546CB505.2070807@balister.org>
Hi,
On 11/19/2014 05:19 PM, Philip Balister wrote:
>
> http://layers.openembedded.org/layerindex/branch/master/duplicates/?l=91&l=123&l=30&l=147&l=168&l=148&l=31&l=65&l=66&l=32&l=124&l=164&l=67&l=149&l=77&l=101&l=118&l=33&l=3&l=34&l=142&l=169&l=35&l=137&l=171&l=139&l=108&l=162&l=81&l=82&l=95&l=125&l=145&l=146&l=114&l=4&l=36&l=68&l=140&l=83&l=132&l=5&l=154&l=120&l=84&l=6&l=93&l=112&l=7&l=37&l=167&l=38&l=8&l=98&l=39&l=165&l=40&l=105&l=69&l=9&l=10&l=110&l=107&l=11&l=12&l=13&l=14&l=41&l=15&l=99&l=151&l=170&l=85&l=42&l=43&l=113&l=159&l=16&l=78&l=92&l=103&l=157&l=97&l=119&l=70&l=152&l=153&l=71&l=126&l=115&l=136&l=44&l=45&l=163&l=17&l=102&l=150&l=46&l=18&l=19&l=79&l=2&l=138&l=174&l=20&l=21&l=128&l=129&l=130&l=131&l=47&l=104&l=48&l=135&l=22&l=173&l=121&l=23&l=160&l=49&l=106&l=24&l=50&l=117&l=143&l=87&l=51&l=52&l=25&l=133&l=116&l=53&l=72&l=122&l=73&l=54&l=55&l=172&l=88&l=109&l=56&l=57&l=100&l=26&l=155&l=90&l=58&l=144&l=59&l=60&l=74&l=61&l=75&l=158&l=134&l=62&l=111&l=27&l=76&l=28&l=141&l=1&l=64
>
> Although that url might fail, you get the idea how to use the tool better :)
The url works for me;)
You just mention duplicated classes and recipes here, but there are more
things which should be cleaned up ;)
The worst thing about Yocto/poky/OE is, that people can do and do things
in many mysterious ways. Looking through various meta-layers you don't
see a "common coding style", which means that you either need to twist
your brain to understand what others did, or write things from scratch.
I guess we should first publish "best practices" and then try to enforce
them in a first step with maybe with something like "WARN_QA" and
"ERROR_QA" and/or extend oelint.
What do you think?
>
> Philip
>
Regards,
Robert
..."Stroustroup writes in the ARM: C programmers think that memory
allocation is too important to be left to the computer, Lisp programmers
think that memory allocation is too important to be left to the programmer."
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2014-11-20 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 21:28 Layer model doomed, unless we all work together Philip Balister
2014-11-18 21:57 ` Burton, Ross
2014-11-18 23:03 ` Martin Jansa
2014-11-19 15:19 ` Philip Balister
2014-11-20 12:04 ` Robert Berger [this message]
2014-11-20 3:34 ` Joe MacDonald
2014-11-20 13:43 ` Paul Eggleton
2014-11-20 15:59 ` Joe MacDonald
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=546DD8C4.6010800@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org \
--cc=yocto@yoctoproject.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.