| Commit message (Collapse) | Author | Age |
| |
|
|\
| |
| | |
doc: update environment helpers in dockerTools docs, add fakeNss section
|
| |
| |
| |
| | |
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
|
|\ \
| | |
| | | |
fix: include reference and link to `outputMan` in the doc of `installManPage`
|
| | | |
|
|\ \ \
| |/ /
|/| | |
doc: clarify usage of nuget-to-nix in dotnet.section.md
|
| | |
| | |
| | |
| | |
| | |
| | | |
I believe it would be helpful to better explain how to use
`nuget-to-nix` for those who aren't familar with the .NET ecosystem as I
was personally stumped on how to use it.
|
|\ \ \
| | | |
| | | | |
docs/dart: Update unstable version example
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
postgresqlTestHook: add postgresqlExtraSettings variable
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add `postgresqlExtraSettings` to allow to setup the `postgresql.conf`.
This would be useful in cases where we need to set
`shared_preload_libraries`.
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
This allows for adding new, conditionally set, derivation attributes
to an existing derivation without changing any output paths in the
case where the condition is not met.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
beam-modules: Fix missing quotation marks
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The given command doesn't work without quotation marks around the expression to
be run.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* doc: update dockerTools.exportImage content and use doc conventions
* Apply suggestions from code review
Co-authored-by: Silvan Mosberger <github@infinisil.com>
---------
Co-authored-by: Silvan Mosberger <github@infinisil.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
doc: consistently use nixpkgs-unstable and "nixpkgs repository"
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rename channel `nixpkgs` to `nixpkgs-unstable`. Based on the
[repo branches](https://github.com/NixOS/nixpkgs/branches)
and [channel status](https://status.nixos.org) I don't believe there is
a `nixpkgs` channel. This confused me as a Nixpkgs beginner.
Rename to `nixpkgs-unstable`, which does exist.
Refer to "nixpkgs repository" consitently. Make the capitalization and
"code quoting" consistent when referring to the repository itself.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`lib.recursiveUpdate` indiscriminately recurses into all attribute sets,
also into derivations. This means that it is possible that evaluating a
derivation in the final haskell package set can cause something in
`prev.haskell` to be forced by `recursiveUpdate`, potentially causing an
evaluation error that should not happen.
It can be fixed using a well-crafted predicate for
`lib.recursiveUpdateUntil`, but most robust is just explicitly writing
out the desired merging manually.
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
treewide: replace `lib/${python.libPrefix}/site-packages` with its sh…
|
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Peder Bergebakken Sundt <pbsds@hotmail.com>
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
`${python.sitePackages}`
which should be always preferred
|
|/ / / / |
|
|\ \ \ \
| |/ / /
|/| | | |
idris2Packages.idris2Lsp: init at 2024-01-21
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
doc: update dockerTools.pullImage content and use doc conventions
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
doc: add figure definition to bespoke syntax reference
doc: add example definition to bespoke syntax reference
doc: add footnote definition to beskpoke syntax reference
The usage of footnotes in the manuals is not the one documented
in markdown-it-py: https://python-markdown.github.io/extensions/footnotes/
doc: add inline comment definition to beskpoke syntax reference
doc: add typographic replacements to beskpoke syntax reference
doc: Fix rendering of bespoke syntax reference
doc: remove references to DocBook in the NixOS manual
doc: add entry on lack of HTML support
doc: Minor improvement
doc: update typographic replacements entry in beskpoke syntax reference
doc: add link reference definitions to beskpoke syntax reference
doc: fix footnote definition in beskpoke syntax reference
doc: Minor improvements from code review
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|\ \ \ \
| | | | |
| | | | | |
doc: add missing attribute to example in dockerTools
|
| |/ / / |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Note on how to use shadowSetup with buildLayeredImage
* Update doc/build-helpers/images/dockertools.section.md
---------
Co-authored-by: Silvan Mosberger <github@infinisil.com>
|
| | | |
| | | |
| | | | |
It should be `dotnetCorePackages.sdk_6_0`, not `dotnetCorePackages.sdk_6.0`
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* doc: add types to template
* mention types explicitly
* use separator that allows for more items in the type declaration
Co-authored-by: Daniel Sidhion <DanielSidhion@users.noreply.github.com>
---------
Co-authored-by: Daniel Sidhion <DanielSidhion@users.noreply.github.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since 46f14d30aa6a57dfdc008901b2d58c54365a0290, it no longer has any
users in nixpkgs.
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
At this point kernel.features is more of an implementation detail and
normal users should not come into contact with it.
|
|\| | | |
|
| |\ \ \
| | |/ /
| |/| | |
Support Web builds in buildFlutterApplication
|
| | | | |
|
| | | | |
|
| | | | |
|
|\| | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
doc: update content on dockerTools.buildImage and follow doc conventions
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
doc: update buildRustPackage documentation
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes some mistakes regarding the references to cargoHash in the codes referenced.
Fixes a typo for cargoSha256.
States that cargoHash should be preferred.
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
doc: mkYarnPackage/mkYarnModules should use offlineCache to prevent IFD
|