| Age | Commit message (Collapse) | Author |
|---|
|
Convert a bunch of comments in headers to Doxygen documentation
|
|
separate man pages for `nix-store` and `nix-env` subcommands
|
|
otherwise the order of found `.md` files will influence if `@docroot@`
is replaced before them being included, which may mess up relative
links.
the weirdest thing about it is that the mess-up happens
deterministically on macOS, but deterministically doesn't happen on
Linux!
|
|
Docs: Explain why `import nixpkgs` works in flakes
|
|
|
|
Allow `@` in git refs
|
|
|
|
Documentation on "classic" commands with many sub-commands are
notoriously hard to discover due to lack of overview and anchor links.
Additionally the information on common options and environment variables
is not accessible offline in man pages, and therefore often overlooked
by readers.
With this change, each sub-command of nix-store and nix-env gets its
own page in the manual (listed in the table of contents), and each own
man page.
Also, man pages for each subcommand now (again) list common options
and environment variables. While this makes each page quite long and
some common parameters don't apply, this should still make it easier
to navigate as that additional information was not accessible on the
command line at all.
It is now possible to run 'nix-store --<subcommand> --help` to display
help pages for the given subcommand.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
The internal API docs now contain more useful information.
Co-authored-by: Théophane Hufschmitt <7226587+thufschmitt@users.noreply.github.com>
|
|
|
|
Co-authored-by: Eelco Dolstra <edolstra@gmail.com>
|
|
Avoid a string copy during Hash::to_string
|
|
|
|
|
|
This fixes the issue that `nix-build`, without experimental feature
'nix-command' enabled, recommends the experimental CLI `nix log` to view
build logs. Now it'll recommend the stable `nix-store -l` CLI instead.
Fixes https://github.com/NixOS/nix/issues/8118
|
|
|
|
Co-authored-by: asymmetric <lorenzo@mailbox.org>
|
|
in order to make the development process more transparent for everyone,
all pull requests should go through the triage process before getting
merged.
this ensures that all team members are aware of what is going on, and
that rationale for decisions is kept track of in the meeting notes for
posterity. (ideally all that should go into the commit history, but this
is a more invasive process change that needs further deliberation.)
having all team members take at least a brief but conscious look at each
change may also help with keeping our quality standards, as more
reviewers are more likely to remind each other of our shared values.
|
|
|
|
Fix more profile dirs in docs
|
|
Picking up where #8078 left off.
|
|
Stratify `ExtraPathInfo` along `Installable` hierarchy
|
|
Auto-generate store documentation
|
|
Fix root channels location
|
|
Add a setting for configuring the SSL certificates file
|
|
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.
|
|
Hide experimental settings
|
|
|
|
nix-store: Use `long` for `narSize` in graphml output
|
|
These are proper documentation of the API, so they deserve to be here
|
|
Catch eval errors in `hasContent`
|
|
|
|
`legacyPackages` of nixpkgs trigger eval errors in `hasContent`, causing
the whole `legacyPackages` being skipped. We should treat it as
has-content in that case.
|
|
|
|
Instead of having a bunch of optional fields, have a few subclasses
which can have mandatory fields.
Additionally, the new `getExtraPathInfo`, and `nixpkgsFlakeRef`, are
moved to `InstallableValue`.
I did these things because https://github.com/NixOS/rfcs/pull/134 ; with
these things moved to `InstallableValue`, the base `Installable` no
longer depends on libexpr! This is a major step towards that.
Also, add a bunch of doc comments for sake of the internal API docs.
|
|
Move value-only methods to `InstallableValue`
|
|
hercules-ci/error-cc-Only-suggest-show-trace-when-truncated-trace-items-would-be-pri
error.cc: Only suggest `--show-trace` when relevant
|
|
Filter tests/nixos from source
|
|
|
|
|
|
Otherwise, a trace consisting of
frame
frame
frame
non-frame
... would reach the non-frame and print the suggestion, even though
it would have ignored the non-frame anyway.
This resulted in a peculariar situation where --show-trace would have
no apparent effect, as the trace was actually already complete.
|
|
|
|
|
|
|
|
|
|
|
|
Make sure that all the code paths use the same one, and that the
backwards-compatibility measures are probably in place when needed
|
|
|
|
|
