max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-10 08:16:15 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
nix-super/doc/manual/opt-common-syn.xml

20 lines
664 B
XML
Raw Normal View History

* Sort `nix-env -q' output by derivation name. * `--version' flag for all commands. * Manual updates.
2004-02-02 12:51:54 +02:00
<arg><option>--help</option></arg>
<arg><option>--version</option></arg>
<arg rep='repeat'><option>--verbose</option></arg>
<arg rep='repeat'><option>-v</option></arg>
* The default verbosity level of all Nix commands is now lvlInfo. * Builder output is written to standard error by default. * The option `-B' is gone. * The option `-Q' suppresses builder output. The result of this is that most Nix invocations shouldn't need any flags w.r.t. logging.
2004-08-18 15:19:06 +03:00
<arg><option>--no-build-output</option></arg>
<arg><option>-Q</option></arg>
* A flag `--keep-going / -k' to keep building goals if one fails, as much as possible. (This is similar to GNU Make's `-k' flag.) * Refactoring to implement this: previously we just bombed out when a build failed, but now we have to clean up. In particular this means that goals must be freed quickly --- they shouldn't hang around until the worker exits. So the worker now maintains weak pointers in order not to prevent garbage collection. * Documented the `-k' and `-j' flags.
2004-06-25 18:36:09 +03:00
<arg>
<group choice='req'>
<arg choice='plain'><option>--max-jobs</option></arg>
<arg choice='plain'><option>-j</option></arg>
</group>
<replaceable>number</replaceable>
</arg>
<arg><option>--keep-going</option></arg>
<arg><option>-k</option></arg>
* Sort `nix-env -q' output by derivation name. * `--version' flag for all commands. * Manual updates.
2004-02-02 12:51:54 +02:00
<arg><option>--keep-failed</option></arg>
<arg><option>-K</option></arg>
* Added a switch `--fallback'. From the manual: Whenever Nix attempts to realise a derivation for which a closure is already known, but this closure cannot be realised, fall back on normalising the derivation. The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository. If the repository is down, the realisation of the derivation will fail. When this option is specified, Nix will build the derivation instead. Thus, binary installation falls back on a source installation. This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
2004-06-28 13:42:57 +03:00
<arg><option>--fallback</option></arg>
* Document --eval-only and --parse-only options in nix-instantiate.
2004-11-13 01:22:08 +02:00
<arg><option>--readonly-mode</option></arg>
Reference in a new issue Copy permalink