[OE-core] [PATCH 2/2] packagegroup-core-x11: split machine specific parts to separate recipe packagegroup-core-x11-server
Martin Jansa
martin.jansa at gmail.com
Thu Sep 6 23:34:13 UTC 2012
On Fri, Sep 07, 2012 at 12:29:59AM +0100, Richard Purdie wrote:
> On Tue, 2012-09-04 at 22:58 +0200, Martin Jansa wrote:
> > * add new packagegroup-core-x11-server to SIGGEN_EXCLUDERECIPES_ABISAFE,
> > so that recipes depending on it are not rebuilt after every machine
> > swtich
> > * allows to remove task-x11-server and task-x11 from meta-oe without
> > loosing any functionality
> > * be carefull with default XSERVER value which does not have
> > xf86-input-mouse and xf86-input-keyboard)
> > * VIRTUAL-RUNTIME_xserver_common which defaults to x11-common in oe-core
> > and xserver-common in meta-oe's task-x11
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa at gmail.com>
> > ---
> > meta/conf/layer.conf | 1 +
> > .../packagegroups/packagegroup-core-x11-xserver.bb | 24 ++++++++++++++++++++++
> > .../packagegroups/packagegroup-core-x11.bb | 16 ++-------------
> > 3 files changed, 27 insertions(+), 14 deletions(-)
> > create mode 100644 meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb
>
> This sneaked in with a load of other patches. I never meant to merge
> this as I consider it broken.
>
> Task packages are cheap and having them being machine specific imposes
> little overhead. Splitting this into two just increases the parsing
> overhead through the number of recipes and doesn't do much else since
> there are still machine specific packages involved, all dependencies
> still get built etc. so I really don't see the point of the added
> complexity.
Yes task-* are cheap but if such recipe is in RDEPENDS of some other
more expensive recipe then it's better when it's excluded from sstate.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120907/a1375116/attachment-0002.sig>
More information about the Openembedded-core
mailing list