mirror of
https://github.com/containers/podman.git
synced 2025-05-17 23:26:08 +08:00
f18c917ef8
This could have been done by simply running
GOOS=freebsd ./bin/golangci-lint run [options] ./...
on Linux, but some freebsd code is using cgo (i.e. is linked to C
libraries), so real freebsd environment is required.
This also fixes the issue of ignoring linter errors for Windows and
Darwin (exit 0), introduced by commit c9b108d5b38.
Fixes: c9b108d5b38 ("Bump golangci-lint to v2.0.2")
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
37 lines
1019 B
Bash
Executable File
37 lines
1019 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# Run golangci-lint with different sets of build tags.
|
|
set -e
|
|
|
|
# WARNING: This script executes on multiple operating systems that
|
|
# do not have the same version of Bash. Specifically, Darwin uses
|
|
# a very old version, where modern features (like `declare -A`) are
|
|
# absent.
|
|
|
|
declare -a EXTRA_TAGS
|
|
|
|
echo "Linting for GOOS=$GOOS"
|
|
case "$GOOS" in
|
|
windows|darwin)
|
|
# For Darwin and Windows, only "remote" linting is possible and required.
|
|
TAGS="remote,containers_image_openpgp"
|
|
;;
|
|
freebsd)
|
|
TAGS="containers_image_openpgp"
|
|
EXTRA_TAGS=(",remote")
|
|
;;
|
|
*)
|
|
# Assume Linux: run linter for various sets of build tags.
|
|
TAGS="apparmor,seccomp,selinux"
|
|
EXTRA_TAGS=(",systemd" ",remote")
|
|
esac
|
|
|
|
for EXTRA in "" "${EXTRA_TAGS[@]}"; do
|
|
# Use set -x in a subshell to make it easy for a developer to copy-paste
|
|
# the command-line to focus or debug a single, specific linting category.
|
|
(
|
|
set -x
|
|
./bin/golangci-lint run --build-tags="${TAGS}${EXTRA}" "$@"
|
|
)
|
|
done
|