From: Denys Dmytriyenko <[email protected]>
* For cases when products based on Arago Core TI-SDK need to select different
providers or versions of packages. For example, AM-SDK needs to stay on the
stable kernel 3.2, while Core TI-SDK is moving to the new kernel 3.8.
* Adding new branding policies requires creating a new branding-<name>.inc file
and setting ARAGO_BRAND=<name> in the local.conf
* The default branding is "core" when ARAGO_BRAND is not set and is mostly empty
to fall back on the default Arago Core TI-SDK preferences.
Denys Dmytriyenko (3):
arago.conf: add branding support to allow products to tweak
preferences
branding-amsdk: add the initial AM-SDK branding policy
arago-prefs: set default preferences to the latest TI staging kernel
and u-boot
meta-arago-distro/conf/distro/arago.conf | 7 +++++++
meta-arago-distro/conf/distro/include/arago-prefs.inc | 9 +++------
meta-arago-distro/conf/distro/include/branding-amsdk.inc | 8 ++++++++
meta-arago-distro/conf/distro/include/branding-core.inc | 6 ++++++
4 files changed, 24 insertions(+), 6 deletions(-)
create mode 100644 meta-arago-distro/conf/distro/include/branding-amsdk.inc
create mode 100644 meta-arago-distro/conf/distro/include/branding-core.inc
--
1.8.1.5
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
