a6e4f94b01
This adds the concept of CustomImagePackage this is similar to the way layers and recipes work in that we have a set of data which is part of the build history and a set of data which is part of the configuration data that toaster uses to guide people in configuring their project. We create a set of built_packages for every build but only create a package for configuration purposes if we don't already have one, so that the CustomImagePackage only ever contains a unique list of packages that are available to be added and removed from a CustomImageRecipe. (Bitbake rev: f81bb65883baa6c0f8a4d48a4de3291a10543992) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: brian avery <avery.brian@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
|---|---|---|
| .. | ||
| crumbs | ||
| icons | ||
| __init__.py | ||
| buildinfohelper.py | ||
| depexp.py | ||
| goggle.py | ||
| hob.py | ||
| knotty.py | ||
| ncurses.py | ||
| puccho.py | ||
| toasterui.py | ||
| uievent.py | ||
| uihelper.py | ||