odroidm1: point updates.url at odroid-m1-bsp-kernel instead of the separate odroid-m1 branch - #5
Merged
Conversation
…parate odroid-m1 branch odroid-m1-bsp-kernel is the actual ongoing release branch (where PR #4 just merged the g29p1/Wayland work) - keeping a separate odroid-m1 branch purely to host the updates/ manifest tree adds an extra branch to remember to update on every release with no real benefit over just committing it here directly. Also copies the current updates/bsp-odroidm1/stable/last/batocera.version manifest (content identical to the released batocera44-odroidm1-v1.0.0 image's own batocera.version) so the new URL resolves immediately - switching the pointer without this would 404 for anyone building from this branch before the next real release. The old odroid-m1 branch is left as-is (not deleted) since the already-shipped v1.0.0 image's batocera.conf still points there - only affects builds from this branch going forward.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
odroid-m1-bsp-kernelis now the actual ongoing release branch (PR #4 just merged the g29p1/Wayland work here). Keeping a separateodroid-m1branch purely to host theupdates/manifest tree adds an extra branch to remember to update on every release, for no real benefit over just committing it here directly.What's in this branch
batocera.conf:updates.urlnow points atodroid-m1-bsp-kernel/updatesinstead ofodroid-m1/updates.updates/bsp-odroidm1/stable/last/batocera.versionhere too (content identical to the releasedbatocera44-odroidm1-v1.0.0image's ownbatocera.version) - switching the pointer without this would 404 for anyone building from this branch before the next real release.Not touched
The old
odroid-m1branch is left as-is (not deleted) - the already-shipped v1.0.0 image'sbatocera.confstill points there, so it needs to keep serving that manifest for existing installs' update-checker to keep working correctly.🤖 Generated with Claude Code