7c4dea3cf3
See the note in the test. We don't want these flags showing up for commands where they are irrelevant. Eventually, this needs a proper fix, but it need not be a blocker for stabilize: for a quick-n-dirty punt, just put these flags behind the `nix-command` unstable feature. This is fine because they are only relevant for commands which we don't need to stabilize for a while.
36 lines
1.3 KiB
Bash
36 lines
1.3 KiB
Bash
source common.sh
|
|
|
|
# Without flakes, flake options should not show up
|
|
# With flakes, flake options should show up
|
|
|
|
function both_ways {
|
|
nix --experimental-features 'nix-command' "$@" | grepQuietInverse flake
|
|
nix --experimental-features 'nix-command flakes' "$@" | grepQuiet flake
|
|
|
|
# Also, the order should not matter
|
|
nix "$@" --experimental-features 'nix-command' | grepQuietInverse flake
|
|
nix "$@" --experimental-features 'nix-command flakes' | grepQuiet flake
|
|
}
|
|
|
|
# Simple case, the configuration effects the running command
|
|
both_ways show-config
|
|
|
|
# Complicated case, earlier args effect later args
|
|
|
|
both_ways store gc --help
|
|
|
|
expect 1 nix --experimental-features 'nix-command' show-config --flake-registry 'https://no'
|
|
nix --experimental-features 'nix-command flakes' show-config --flake-registry 'https://no'
|
|
|
|
# Double check this is stable
|
|
nix --experimental-features '' --help
|
|
|
|
# These 3 arguments are currently given to all commands, which is wrong (as not
|
|
# all care). To deal with fixing later, we simply make them require the
|
|
# nix-command experimental features --- it so happens that the commands we wish
|
|
# stabilizing to do not need them anyways.
|
|
for arg in '--print-build-logs' '--offline' '--refresh'; do
|
|
nix --experimental-features 'nix-command' "$arg" --help
|
|
! nix --experimental-features '' "$arg" --help
|
|
done
|