openFyde anchors revisions of upstream projects in file chromiumos.xml:
<manifest>
<!-- .... -->
<extend-project name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="refs/heads/release-R96-14268.B-fydeos" origRev="refs/heads/release-R96-14268.B" />
<extend-project name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="release-R96-14268.B-fydeos" origRev="refs/heads/release-R96-14268.B" />
<extend-project name="chromium/tools/depot_tools" path="src/chromium/depot_tools" revision="release-R96-14268.B-fydeos" origRev="09f358bae36c316e3c4c39cd344de964bd0fed7c" />
<!-- .... -->
</manifest>Basically, chromiumos.xml doesn't change in one release life cycle.
The openfyde.xml contains projects which openFyde owns.
The projects are necessary for building openFyde for board amd64-openfyde.