summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRicardo Salveti <ricardo@opensourcefoundries.com>2018-05-18 17:47:11 -0300
committerLaurent Bonnans <laurent.bonnans@here.com>2019-08-15 17:48:39 +0200
commit7c7aec62e844e79e862cb9ac49ca9f73c5931629 (patch)
treebfe4bf568683728e13b43d7e324ed95726714d81
parentfe8e93af15a0698a7f20883a5b7fdcde7c10c5f5 (diff)
downloadmeta-updater-7c7aec62e844e79e862cb9ac49ca9f73c5931629.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> (cherry-picked from commit 54f9b8e2ecb4ef0027da026368edc33bbc08eed4)
-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 79147cf..ca97fdb 100644
--- a/classes/image_types_ostree.bbclass
+++ b/classes/image_types_ostree.bbclass
@@ -119,12 +119,6 @@ IMAGE_CMD_ostree () {
119 ln -sf var/roothome root 119 ln -sf var/roothome root
120 fi 120 fi
121 121
122 # Creating boot directories is required for "ostree admin deploy"
123
124 mkdir -p boot/loader.0
125 mkdir -p boot/loader.1
126 ln -sf boot/loader.0 boot/loader
127
128 checksum=`sha256sum ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} | cut -f 1 -d " "` 122 checksum=`sha256sum ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} | cut -f 1 -d " "`
129 123
130 cp ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} boot/vmlinuz-${checksum} 124 cp ${DEPLOY_DIR_IMAGE}/${OSTREE_KERNEL} boot/vmlinuz-${checksum}