Chris Larson 9f33dde6e7 cooker: use BBHandler.inherit for INHERIT ... Ideally we'd avoid direct BBHandler usage, but honestly, to say the whole bb.parse abstraction is incredibly leaky is an understatement. If we try to make handle() not reparse classes, things get ugly fairly quickly, as inherit() calls handle() itself after adding the class to the inherit cache. This change fixes it so we no longer risk reparsing a class if: - it's listed in INHERIT multiple times - it's listed in INHERIT and is 'inherit'ed from a class in INHERIT (Bitbake rev: 057c3cddeb72584c6c3908bd702288cece9b66ea) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2011-06-08 20:38:26 +01:00
..
bb	cooker: use BBHandler.inherit for INHERIT	2011-06-08 20:38:26 +01:00
ply	Add pysh, ply, and codegen to lib/ to prepare for future work	2010-08-03 14:06:07 +01:00
prserv	Add PR service deamon to bitbake	2011-05-27 17:55:49 +01:00
codegen.py	Add pysh, ply, and codegen to lib/ to prepare for future work	2010-08-03 14:06:07 +01:00
progressbar.py	Experimental usage of the 'progressbar' module	2011-01-04 14:46:42 +00:00