kirkstone-backport: classes: genimage: generalize image symlink creation #160
Conversation
This file contains 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
A genimage config may generate multiple images, either because multiple
image { } clauses are specified or because an exec-post generated
further images (e.g. image { exec-post = "gzip -k $IMAGEOUTFILE" })
We already deploy these extra images, but currently symlinks are only
created for the plain image and for the bmap file. Make this more
generic, so fixed symlinks are created at least for all images
using @image@ as part of their filename.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
[ahmad: backport from 518d3c6]
a3f
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A genimage config may generate multiple images, either because multiple image { } clauses are specified or because an exec-post generated further images (e.g. image { exec-post = "gzip -k $IMAGEOUTFILE" })
We already deploy these extra images, but currently symlinks are only created for the plain image and for the bmap file. Make this more generic, so fixed symlinks are created at least for all images using @image@ as part of their filename.
Signed-off-by: Ahmad Fatoum a.fatoum@pengutronix.de
[ahmad: backport from 518d3c6]
I need this, because the BSP I work on has a sparse image with a name that keeps changing and I want a fixed symlink to point at it.