From 298504a03124888787c6ef3249c8a1923a50a5d6 Mon Sep 17 00:00:00 2001 From: LordMZTE Date: Tue, 10 May 2022 13:30:16 +0200 Subject: [PATCH] fix: properly install dependencies in containers --- docs/content/builder.md | 2 +- src/build/build.v | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/builder.md b/docs/content/builder.md index ccd2427b..1c15208d 100644 --- a/docs/content/builder.md +++ b/docs/content/builder.md @@ -15,7 +15,7 @@ repositories. After the image has been created, each repository returned by previously created image as a base. Each container goes through the following steps: 1. The repository is cloned -2. `makepkg --nobuild` is ran to update the `pkgver` variable inside +2. `makepkg --nobuild --syncdeps --noconfirm` is ran to update the `pkgver` variable inside the `PKGBUILD` file 3. A HEAD request is sent to the Vieter server to check whether the specific version of the package is already present. If it is, the container exits. diff --git a/src/build/build.v b/src/build/build.v index d4fbfc7e..64ebda0e 100644 --- a/src/build/build.v +++ b/src/build/build.v @@ -91,7 +91,7 @@ pub fn build_repo(address string, api_key string, base_image_id string, repo &db commands := [ 'git clone --single-branch --depth 1 --branch $repo.branch $repo.url repo', 'cd repo', - 'makepkg --nobuild', + 'makepkg --nobuild --syncdeps --noconfirm', 'source PKGBUILD', // The build container checks whether the package is already // present on the server