| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
cudaPackages standard
|
| | |
|
| |
|
|
|
| |
That sort of formatting wouldn't be accepted into Nixpkgs. We shouldn't format
an example like that.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
doc/languages-frameworks/python: update formatting and interpreters
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Updates all interpreter references with 3.10/3.11, which are the
current version, that we recurse into for their package set.
Update all code examples with an explicit `format` and expand lists
with multiple items as we do in the python package set. Also set
`pythonImportsCheck` where tests are disabled.
|
| |/
|
| |
t0 is mentioned in the conclusion so we cannot use placeholder in the premise.
|
| |
|
|
| |
This will be deprecated in the next commit.
|
| |\
| |
| | |
testers.runNixOSTest: init
|
| | |
| |
| |
| | |
An up to date alternative to pkgs.nixosTest
|
| |\ \
| |/
|/| |
buildDartApplication: init
|
| | | |
|
| | |
| |
| |
| | |
This adds a function for easily packaging non-flutter dart apps.
|
| |\ \
| | |
| | | |
doc: update shortenPerlShebang example to use nativeBuildInputs
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | | |
module system: Improve error messages around faulty imports
|
| | | |
| | |
| | |
| | | |
This simplifies the documentation. `configuration` is implied by `_type`.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows modules that declare their class to be checked.
While that's not most user modules, frameworks can take advantage
of this by setting declaring the module class for their users.
That way, the mistake of importing a module into the wrong hierarchy
can be reported more clearly in some cases.
|
| |\ \ \
| |/ /
|/| | |
treewide: switch builtins.fromJSON(builtins.readFile ./file.json) to …
|
| | |/
| |
| |
| | |
lib.importJSON ./file.json #2
|
| |/ |
|
| |
|
|
|
| |
* doc/default.nix: make the manual build on more than one core
Let's build the manual with more than one core. Maybe people will take better care of it now that it is less painful to build.
|
| |
|
|
|
| |
Versioned package attributes are usually named like $pname_$version
eg: nodejs-14_x -> nodejs_14
|
| |
|
|
|
|
|
| |
* doc/stdenv/meta.chapter.md: document meta.badPlatforms
We don't have any documentation for the `meta.badPlatforms` attribute.
This commit adds documentation for it.
|
| |\
| |
| | |
doc/stdenv/meta.chapter.md: explain difference between broken and badPlatforms
|
| | | |
|
| | |
| |
| | |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| | |
| |
| | |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There has been a longstanding ambiguity between `broken` and
`badPlatforms`, which seem to serve overlapping purposes.
This commit adds to the documentation two examples of constraints
which cannot be expressed by `platforms` and `badPlatforms`.
This commit also mentions `NIXPKGS_ALLOW_BROKEN=1` for overriding
`broken`.
|
| | |
| |
| |
| | |
https://www.haskell.org/ghc/blog/20230418-ghc-9.4.5-released.html
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* buildGoModule: don't inherit postBuild hook when building go-modules
This is a slight revert of 5ce647b8bf7aee0d3862006d94df7878c7fc03a6
(#212800).
Inheriting these hooks in the `.go-modules` derivation can be confusing:
One doesn't expect them to run when generating the fixed output modules
derivation, but only on the main derivation. A `postBuild` hook that
adds some files to $out will cause a very hard to debug issue[1].
This commit adds support for a dedicated `modPostBuild` hook that will
be used only by the derivation building `.go-modules`. Additionally,
`go.section.md` now explains these attributes behavior better.
[1]:
https://discourse.nixos.org/t/cant-update-a-go-package-getting-go-inconsistent-vendoring/27063/6
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
| |\ \
| | |
| | | |
buildFHSEnv: use bubblewrap by default
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* update.py: introduce subparsers for plugin updaters
This is preliminary work to help create more powerful plugin updaters.
Namely I would like to be able to "just add" plugins without refreshing
the older ones (helpful when github temporarily removes a user from
github due to automated bot detection).
Also concerning the lua updater, we pin some of the dependencies, and I
would like to be able to unpin the package without editing the csv
(coming in later PRs).
* doc/updaters: update command to update editor plugins
including vim, kakoune and lua packages
Co-authored-by: figsoda
|
| | |
| |
| | |
environements -> environments
|
| |\ \
| | |
| | | |
doc: Fix the function locations always pointing to master
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Instead of revisions as they should. This is (most-likely) caused by a
simple typo, because Hydra is where the revision should come from, but
it doesn't set `.revision` as the attribute, but rather `.rev`!
|
| |\ \ \
| | | |
| | | | |
Documentation: add vmTools
|