| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
Co-authored-by: cole-h <cole.e.helbling@outlook.com>
Co-authored-by: asymmetric <lorenzo@mailbox.org>
|
| |/
|
|
| |
See also https://discourse.nixos.org/t/rust-build-speed-improvements/7225
|
| |
|
|
|
|
|
| |
We have now migrated every single Rust package in NixPkgs! This deletes the
legacy fetcher, which is now unused.
Resolves #79975
|
| |
|
|
|
|
|
|
|
|
| |
Previously, we would asssert that the lockfiles are consistent during the
unpackPhase, but if the pkg has a patch for the lockfile itself then we must
wait until the patchPhase is complete to check.
This also removes an implicity dependency on the src attribute coming from
`fetchzip` / `fetchFromGitHub`, which happens to name the source directory
"source". Now we glob for it, so different fetchers will work consistently.
|
| | |
|
| |
|
|
|
| |
As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified
is now `false`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has several advantages:
1. It takes up less space on disk in-between builds in the nix store.
2. It uses less space in the binary cache for vendor derivation packages.
3. It uses less network traffic downloading from the binary cache.
4. It plays nicely with hashed mirrors like tarballs.nixos.org, which only
substitute --flat hashes on single files (not recursive directory hashes).
5. It's consistent with how simple `fetchurl` src derivations work.
6. It provides a stronger abstraction between input src-package and output
package, e.g., it's harder to accidentally depend on the src derivation at
runtime by referencing something like `${src}/etc/index.html`. Likewise, in
the store it's harder to get confused with something that is just there as a
build-time dependency vs. a runtime dependency, since the build-time
src dependencies are tarred up.
Disadvantages are:
1. It takes slightly longer to untar at the start of a build.
As currently implemented, this attaches the compacted vendor.tar.gz feature as a
rider on `verifyCargoDeps`, since both of them are relatively newly implemented
behavior that change the `cargoSha256`.
If this PR is accepted, I will push forward the remaining rust packages with a
series of treewide PRs to update the `cargoSha256`s.
|
| |
|
|
|
| |
We should not encourage installing build-tooling system-wide but
instead promote nix-shell.
|
| |
|
|
| |
The example in the manual was out of date and didn't use the newer `pname`
convention, which simplifies the fetch call.
|
| | |
|
| |\
| |
| | |
build-support/rust: Add target option
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
Reorganize the chapters into parts and reduce the TOC depth to make the
TOC useful again. The top-level TOC is very brief, but that is fine
because every part will have its own TOC.
Section titles of languages/frameworks are also simplified to just
the name of the language/framework.
|
| |
|
|
|
|
|
|
|
|
|
| |
One issue with cargoSha256 is that it's hard to detect when it needs to
be updated or not. It's possible to upgrade a package and forget to
update cargoSha256 and run with old versions of the program or
libraries.
This commit introduces `verifyCargoDeps` which, when enabled, will check
that the Cargo.lock is not out of date in the cargoDeps by comparing it
with the package source.
|
| |
|
|
| |
The previous one didn't work, returning a TOML parse error.
|
| | |
|
| |
|
| |
nixcrate is deprecated
|
| |
|
|
|
| |
Want to get this out of here for 18.09, so it can be deprecated
thereafter.
|
| | |
|
| |
|
|
|
|
|
| |
- Add example for setting up nix-shell, improve rust docs
- Rust docs: add gcc rust dependencies and fix carnix commands
- Fix a typo with the carnix command.
|
|
|
This makes a makefile-driven developer workflow nicer.
|