fix: don't pass --nodeps to initial build step (#173)

This fixes packages that require their dependencies in `pkgver` or
`prepare` failing to build.

Reviewed-on: vieter/vieter#173
Co-authored-by: LordMZTE <lord@mzte.de>
Co-committed-by: LordMZTE <lord@mzte.de>
LordMZTE 2022-05-10 13:36:07 +02:00 committed by Jef Roosens
parent 78fc3afcd3
commit 0bac221aee
2 changed files with 2 additions and 2 deletions

View File

@ -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 --nodeps` is ran to update the `pkgver` variable inside
2. `makepkg --nobuild --syncdeps --needed --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.

View File

@ -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 --nodeps',
'makepkg --nobuild --syncdeps --needed --noconfirm',
'source PKGBUILD',
// The build container checks whether the package is already
// present on the server