Skip to content

Rework this branch to Blacksail release - #14

Open
lucianogdittgen wants to merge 1 commit into
OSSystemsEmbeddedLinux:blacksailfrom
lucianogdittgen:release/blacksail
Open

lucianogdittgen wants to merge 1 commit into
OSSystemsEmbeddedLinux:blacksailfrom
lucianogdittgen:release/blacksail

Conversation

@lucianogdittgen

Copy link
Copy Markdown
Contributor

Turns the new blacksail branch (cut from master at a3a4186) into a release manifest, the way scarthgap was done:

  • default.xml: default revision blacksail, BitBake 2.20 (OE-Core blacksail needs >= 2.19.1); ye stays on master
  • README and modifying-platform.md: repo init -b blacksail and the manifest shown inline

ossystems-yocto-base-scripts now has a blacksail branch (cut from master, the scripts are release-agnostic).

Merge after OSSystemsEmbeddedLinux/meta-ossystems-base#153: meta-ossystems-base blacksail still says LAYERSERIES_COMPAT = "wrynose", so a fresh checkout of this manifest fails to parse until that PR lands.

Tested: repo init -b release/blacksail + repo sync in a scratch directory, meta-ossystems-base at #153's head, MACHINE=qemux86-64 DISTRO=oel: bitbake -p 0 errors, bitbake -n core-image-minimal OK (BitBake 2.20.0).

Track blacksail for every project without an explicit revision and BitBake
2.20, the branch OE-Core blacksail requires; ye stays on master. The README
and the manifest walkthrough name the branch to repo init.

Signed-off-by: Luciano Dittgen <luciano.dittgen@ossystems.com.br>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant