Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using Yocto 2.3 Pyro release through testing and stable branch.
For newer Yocto release there are rocko, sumo, thud, master branches and unstable points to one of them. These branches are for testing against new Yocto, (but not very often tested on target).
Layerman will take care of the checkout of right layers with right revisions - just type make update if you want newer.
The Yocto upgrade was blocked by very old mesa we're still using in pyro, there was some progress recently, so hopefully we'll move forward soon.
Currently failing builds with new Yocto:
Yocto 2.5 Sumo
ERROR: initramfs-android-recovery-tissot-3.1.1-1-r0 do_package_qa: QA Issue: /recovery/sbin/permissive.sh contained in package initramfs-android-recovery-tissot requires /sbin/sh, but no providers found in RDEPENDS_initramfs-android-recovery-tissot? [file-rdeps] http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_tissot/12/console fixed in thud and master, now cherry-picked to sumo as well
Yocto 2.6 Thud
kernel and gcc8
http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_hammerhead/37/console http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_mako/122/console http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_onyx/1/console http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_tenderloin/121/console
mtp-server meta-webos-ports/meta-luneos/recipes-luneos/mtp-server/mtp-server_git.bb:do_configure http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_tissot/11/consoleFull http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_rosy/10/console http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_mido/11/console fixed in master, will get it backported to thud later
Yocto 2.7 Warrior (master)
Very old Overview
Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using dylan release, master is sometimes updated to test newer stuff in upstream layers (but not very often tested on target).
Layerman will take care of checkouting right layers with right revisions - just type make update if you want newer.
Current (as of right now 21th September 2013) we're using this set of layers:
- changes in our meta-webos fork (meta-webos-ports repository) are described here MetaWebosCommits
webos-ports-setup/master (this will be renamed when new oe-core 1.5 is released - master always tracks master in upstream layers)
Branch name prefixed with 'webOS-ports/', means we're modifying some upstream repository. webOS-ports/danny, webOS-ports/dylan also means that this modification is compatible with older danny, dylan branches and also indicates that this branch is sometimes rebased on danny, dylan branch in upstream repository.
Where to push changes: meta-webos-ports: master branch meta-smartphone: please try to push all changes to webOS-ports/master *and* shr (compatible with master) branches. meta-smartphone/shr is merged to meta-smartphone/master (when there isn't explicit dependency on other shr branches) and after that webOS-ports/master is rebased from meta-smartphone/master. If some change isn't pushed to "shr" branch, then there is a risk that we'll forget to forward-port that change when moving to next release. oe-core: webOS-ports/master
Branches which are rebased now have git tags with date when it was rebased (this way we can continue to use older revisions, which are no longer in branch after last rebase).