build_chroot: Let eopkg handle system.base order

Recent changes implies that baselayout should always get installed first. Signed-off-by: Rune Morling <[email protected]>
getsolus · Jun 29, 2024 · 277eb50 · 277eb50
1 parent ee1798c
commit 277eb50
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/build_chroot.sh b/build_chroot.sh
@@ -171,8 +171,8 @@ basicSetup () {
     printInfo "${MSG}"
     ${eopkg_py3} remove-repo Solus -D "${SOLROOT}" || die "${MSG}"
 
-    MSG="Installing baselayout ..."
-    ${eopkg_py3} install -y -D "${SOLROOT}" --ignore-safety --ignore-comar baselayout || die "${MSG}"
+    #MSG="Installing baselayout ..."
+    #${eopkg_py3} install -y -D "${SOLROOT}" --ignore-safety --ignore-comar baselayout || die "${MSG}"
 
     # Since we're testing eopkg.py3 from a venv, let's use that instead for creating the root
     #MSG="Installing packages to act as a seed for systemd-nspawn chroot runs ..."