Skip to content
Snippets Groups Projects
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
default.xml 4.78 KiB
<?xml version="1.0" encoding="UTF-8"?>
<!--
SPDX-License-Identifier: Apache-2.0
SPDX-FileCopyrightText: Huawei Inc.
-->
<manifest>
	<notice>

		Thank you for building a development version of Oniro Project.
		This manifest file automatically follows changes in certain
		layers and is suitable for development of Oniro Project itself.

		Check out Oniro Project documentation at https://docs.oniroproject.org

		Meet the developers on mattermost at https://chat.booting.oniroproject.org/

	</notice>
	<remote name="github" fetch="https://github.com" />
	<remote name="oniro" fetch="https://booting.oniroproject.org/distro" />
	<remote name="oniro-governance" fetch="https://booting.oniroproject.org/distro/governance" />
	<remote name="yocto" fetch="git://git.yoctoproject.org" />
	<remote name="openembedded" fetch="git://git.openembedded.org" />
	<remote name="aehs29" fetch="https://github.com/aehs29" />
	<remote name="seco-intel" fetch="https://git.seco.com/pub/intel/yocto" />
	<remote name="seco-imx" fetch="https://git.seco.com/pub/i.mx/yocto/5.x" />
	<remote name="stm" fetch="https://github.com/STMicroelectronics" />
	<remote name="linaro" fetch="https://git.linaro.org/openembedded" />
	<remote name="oe" fetch="git://git.openembedded.org" />

	<!--
		Oniro Project build system is based on Yocto "dunfell"
		(3.1 - see https://wiki.yoctoproject.org/wiki/Releases for more information).
		Hence, the layers setup below uses corresponding "dunfell" layers or "dunfell" compatible revisions.
	-->

	<default remote="oniro" revision="kirkstone" sync-j="4" />
	<!--
		dunfell is using the 1.46 bitbake branch so the bitbake project follow is following this branch.
		More info can be found at https://wiki.yoctoproject.org/wiki/Releases.
	-->
	<project name="bitbake" remote="oe" revision="f1a3e9d22b5f4fb01c4a0e4ba03afb1afbba47f1" path="bitbake" />
	<project name="openembedded-core" remote="oe" revision="44b1970c40e9d73f6e63fb10cdc55837a26f5921" path="oe-core" />
	<project name="meta-openembedded" remote="openembedded" revision="7889158dcd187546fc5e99fd81d0779cad3e8d17" path="meta-openembedded" />
	<project name="meta-freertos" remote="aehs29" revision="f3c2edb0f22c34b35a775c5d17ea1424d44bee21" path="meta-freertos" />
	<project name="meta-st-stm32mp" remote="stm" revision="b25a2b0daa6e9e1e3ce76b9fdf5bd7cbf30e90fc" path="meta-st-stm32mp" />
	<project name="meta-st-stm32mp-addons" remote="stm" revision="81065195a63e98be8f423ab422960e9d7896f4d5" path="meta-st-stm32mp-addons" />

	<project name="meta-intel" remote="yocto" revision="b4e5d33affeaa223459c0935a853485137b4591d" path="meta-intel" />
	<project name="meta-seco-intel" remote="seco-intel" revision="baf4cd3237bdf4f4999b7d44c6992dbcab93d5e3" path="meta-seco-intel" />

	<project name="meta-freescale" remote="yocto" revision="11170950b155168ec414bbde48e3a4427fcac4bd" path="meta-freescale" />
	<project name="meta-seco-imx" remote="seco-imx" revision="986dd20885277df45d2acc6e38823bf4c64f0085" path="meta-seco-imx" />
	<project name="meta-av96" revision="a4b2b45efcbad1882227eac54b5023ff6b736b10" path="meta-av96" />
	<project name="meta-python-mixin" revision="7bda3c1e5d6876375a8bf865ed9fcce2622c1715" path="meta-python-mixin" />
	<project name="meta-raspberrypi" remote="yocto" revision="934064a01903b2ba9a82be93b3f0efdb4543a0e8" path="meta-raspberrypi" />
	<project name="meta-security" remote="yocto" revision="b76698c788cb8ca632077a972031899ef15025d6" path="meta-security" />
	<project name="meta-linaro" remote="linaro" revision="10af9133aeb28b3487fd227c900c11b786505699" path="meta-linaro" />
	<project name="rauc/meta-rauc.git" remote="github" revision="f528f95b75922eb81895d764836a67f13858365a" path="meta-rauc" />

	<!--
		All entries above are pinned to a specific revision and updated manually.

		For the entries below this comment it depends on the phase of development
		the project is in at the given time. In normal development mode it would be
		"floating" entries, that follow branches and not precise revisions (this
		can be identified by the missing revision="" tag).

		When the release process is entered these would be pinned as well. Most
		likely to a git tag in the repository. If a revision="" tag is present
		this is the case.

	-->

	<project name="oniro" revision="kirkstone" path="oniro">
		<linkfile src="README.md" dest="README.md"/>
	</project>
	<project name="meta-arm-dunfell-backports" revision="dunfell" path="meta-arm-mixin" />
	<project name="meta-clang" revision="main" path="meta-clang" />
	<project name="meta-riscv" revision="OSTC/dunfell" path="meta-riscv" />
	<project name="meta-zephyr" revision="ostc/master" path="meta-zephyr" />
        <project name="meta-zephyr-bsp" revision="dunfell" path="meta-zephyr-bsp" />
	<project name="docs" path="docs" revision="main" />
	<project name="ip-policy" remote="oniro-governance" revision="main" path="ip-policy" />
</manifest>