summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRicardo Salveti <ricardo@opensourcefoundries.com>2018-05-18 17:47:11 -0300
committerRicardo Salveti <ricardo@opensourcefoundries.com>2018-06-12 17:23:58 -0300
commit54f9b8e2ecb4ef0027da026368edc33bbc08eed4 (patch)
tree52207c964bee2198c4ae3f1e533410973674118b
parent642559cd005076bc4f53fd066b8ce4a62be72864 (diff)
downloadmeta-updater-54f9b8e2ecb4ef0027da026368edc33bbc08eed4.tar.gz
image_types_ostree: no need to create boot/loader folders when creating ostree repo
The boot/loader folders are only required at the deploy stage, which is already created by image_types_ota.bbclass. Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
-rw-r--r--classes/image_types_ostree.bbclass6
1 files changed, 0 insertions, 6 deletions
diff --git a/classes/image_types_ostree.bbclass b/classes/image_types_ostree.bbclass
index bc44e33..6aacc52 100644
--- a/classes/image_types_ostree.bbclass
+++ b/classes/image_types_ostree.bbclass
@@ -121,12 +121,6 @@ IMAGE_CMD_ostree () {
121 cp ${SOTA_SECONDARY_ECUS} var/sota/ecus 121 cp ${SOTA_SECONDARY_ECUS} var/sota/ecus
122 fi 122 fi
123 123
124 # Creating boot directories is required for "ostree admin deploy"
125
126 mkdir -p boot/loader.0
127 mkdir -p boot/loader.1
128 ln -sf boot/loader.0 boot/loader
129
130 checksum=`sha256sum ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} | cut -f 1 -d " "` 124 checksum=`sha256sum ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} | cut -f 1 -d " "`
131 125
132 cp ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} boot/vmlinuz-${checksum} 126 cp ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} boot/vmlinuz-${checksum}