| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
buildRustPackage: add cargoDepsName attribute
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The directory in the tarball of vendored dependencies contains `name`,
which is by default set to `${pname}-${version}`. This adds an
additional attribute to permit setting the name to something of the
user's choosing.
Since `cargoSha256`/`cargoHash` depend on the name of the directory of
vendored dependencies, `cargoDepsName` can be used to e.g. make the
hash invariant to the package version by setting `cargoDepsName =
pname`.
|
|\ \ \
| | | |
| | | | |
pytestCheckHook: add support for disabling arbitrary paths
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Renames `disabledTestFiles` to the more genereric `disabledTestPaths` to
reflect that change.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
API change:
`cargoParallelTestThreads` suggests that this attribute sets the
number of threads used during tests, while it is actually a boolean
option (use 1 thread or NIX_BUILD_CORES threads). In the hook, this
is replaced by a more canonical name `dontUseCargoParallelTests`.
|
|/ / / |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| / /
| |/ / |
|
| | | |
|
|/ / |
|
| | |
|
|\| |
|
| |\
| | |
| | | |
agda.withPackages: use GHC with ieee754 as default
|
| | |
| | |
| | |
| | |
| | | |
As mentioned in the package description of ieee on Hackage,
ieee is deprecated in favor of ieee754.
|
| | | |
|
| | | |
|
|/ / |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* doc: add function argument order convention
Ordering by usage is the de facto ordering given to arguments. It's
logical, and makes finding argument usage easier. Putting lib first is
common in NixOS modules, so it's reasonable to mirror this in nixpkgs
proper. Additionally, it's not a package as such, has zero dependencies,
and can be found used anywhere in a derivation.
* doc: clean up usage of lib
|
|\| |
|
| | |
|
|\| |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise pasting the snippet into shell.nix results in:
error: syntax error, unexpected '=', expecting $end, at /.../shell.nix:2:9
Signed-off-by: Alexei Colin <ac@alexeicolin.com>
|
|/ / |
|
|\| |
|
| |\
| | |
| | | |
r-modules: Updated definitions of CRAN and Bioc packages.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The last snapshot was 4 months ago (2020-08-19). I also found that I needed newer definitions when I was trying to fix the R arrow package.
This update required a couple of manual changes:
1. Removing a few deleted packages from default.nix
2. Renaming the "assert" package to "r_assert" in generate-r-packages.R because "assert" is a keyword in Nix
|
| | |
| | |
| | | |
changing bullet style
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of: https://github.com/NixOS/nixpkgs/issues/108938
Changing the documentation to not refer to stdenv.lib is the first
step to make people use it directly.
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
The library does not depend on stdenv, that `stdenv` exposes `lib` is
an artifact of the ancient origins of nixpkgs.
|
|\| | |
|
| |\ \ |
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
androidenv did not previously write license files, which caused certain
gradle-based Android tools to fail. Restructure androidenv's list of
Android packages into a single repo.json file to prevent duplication
and enable us to extract the EULA texts, which we then hash with
builtins.hashString to produce the license files that Android gradle
tools look for.
Remove includeDocs and lldbVersions, as these have been removed
from the Android package repositories.
Improve documentation and examples.
|
|/ / |
|
|/ |
|
|\
| |
| | |
doc: explicit Markdown anchors for top-level headings; remove metadata
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I used the existing anchors generated by Docbook, so the anchor part
should be a no-op. This could be useful depending on the
infrastructure we choose to use, and it is better to be explicit than
rely on Docbook's id generating algorithms.
I got rid of the metadata segments of the Markdown files, because they
are outdated, inaccurate, and could make people less willing to change
them without speaking with the author.
|
|/ |
|
|
|
|
| |
This will allow patching extensions without having to manually having to patch all occurrences in the dependency tree.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|