From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: OEDEM: Summary of the 'Splitting the tree' session
Date: Thu, 12 Nov 2009 09:29:00 +0100 [thread overview]
Message-ID: <1258014540.6879.18.camel@opal> (raw)
Hi guys,
here's the summary of the 'splitting the tree' session:
Nobody seems to disagree with splitting the metadata tree into more
managable chunks. The expected goals are:
1. Making it easier to find things,
2. Being able to mask whole groups out for improved parsing
3. Identifying core code which needs to always work, hence improving the
observed quality of OE.
Several criteria for splitting were discussed and there was a consensus
for splitting by functional complex. A tentative list of directories to
be used is:
base (10% underlying recipes)
toolchain
x11
framebuffer
gtk (includes gnome apps)
qte (includes opie and kde)
efl
The attendendees were well aware of all the inherent problems with
taxonomy and its different meaning to anybody in the first place as well
as that some recipes will always be difficult to categorize since they
are very flexible to configure. This did not prevent the consensus that
splitting up will be necessary to improve quality.
It was noted that oestats should be enhanced to be able to report a
subset of stats to start developing a test matrix of things which should
always work.
More discussion shall be carried on on this list and after the TSC has
been elected, it will make a final decision.
Cheers,
:M:
next reply other threads:[~2009-11-12 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 8:29 Michael 'Mickey' Lauer [this message]
2009-11-12 8:38 ` OEDEM: Summary of the 'Splitting the tree' session Frans Meulenbroeks
2009-11-12 23:35 ` Detlef Vollmann
2009-11-13 10:11 ` Frans Meulenbroeks
2009-11-12 23:26 ` Detlef Vollmann
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=1258014540.6879.18.camel@opal \
--to=mickey@vanille-media.de \
--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.