mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-11-22 05:56:15 +02:00
docs: clarify how the different kinds of installables are selected
Change-Id: I146736bb97ebe035e04be69ce9fb60a557e38c6c
This commit is contained in:
parent
733c816d34
commit
8ff169715d
1 changed files with 4 additions and 0 deletions
|
@ -59,9 +59,13 @@ These are command line arguments that represent something that can be realised i
|
|||
The following types of installable are supported by most commands:
|
||||
|
||||
- [Flake output attribute](#flake-output-attribute) (experimental)
|
||||
- This is the default
|
||||
- [Store path](#store-path)
|
||||
- This is assumed if the argument is a Nix store path or a symlink to a Nix store path
|
||||
- [Nix file](#nix-file), optionally qualified by an attribute path
|
||||
- Specified with `--file`/`-f`
|
||||
- [Nix expression](#nix-expression), optionally qualified by an attribute path
|
||||
- Specified with `--expr`/`-E`
|
||||
|
||||
For most commands, if no installable is specified, `.` is assumed.
|
||||
That is, Nix will operate on the default flake output attribute of the flake in the current directory.
|
||||
|
|
Loading…
Reference in a new issue