Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish raw and flasher images separately #193

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mtoman
Copy link
Contributor

@mtoman mtoman commented Mar 9, 2021

At this moment we only publish a single balena.img which is either a flasher image or a raw image based on the device configuration. There is no simple way of telling the type without looking at the metadata. We also want to publish both raw and flasher images for devices that use flasher. This patch adds two new files balena-raw.img and balena-flasher.img while keeping the original balena.img for backwards compatibility.

Please be aware that after merge this will mean double disk space consumption for non-flasher DTs and triple disk space consumption for DTs that use flasher.

mtoman added 3 commits March 9, 2021 06:13
…her images

At this moment we are providing a single balena.img file that is either
raw or flasher based on the coffee script. We want to publish both
for some device types, therefore split the single file into balena-raw.img
and balena-flasher.img.

Temporarily keep the existing balena.img for backwards compatibility until
all coffee scripts are updated and image maker is aware of the split.

Change-type: minor
Signed-off-by: Michal Toman <[email protected]>
No functional change, just refactor a section of the script to make
it more readable.

Change-type: patch
Signed-off-by: Michal Toman <[email protected]>
@mtoman mtoman force-pushed the publish_raw_and_flasher branch from 6d979c2 to 1b34cd9 Compare March 9, 2021 05:14
@mtoman mtoman requested review from alexgg, floion and klutchell March 9, 2021 05:15
Copy link
Collaborator

@alexgg alexgg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mtoman it's been a while since this was discussed, what was the motivation for this again?

I would rather not keep three copies of the image. We should push for the image maker change to be done first, and then we can remove the balena.zip file. Device integration layers will adapt their coffee files as they update to new balena-yocto-scripts versions.

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.

2 participants