| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
| |
We have now migrated every single Rust package in NixPkgs! This deletes the
legacy fetcher, which is now unused.
Resolves #79975
|
| |\
| |
| | |
androidenv: enhance script for the generated expressions
|
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
I din't try to pinpoint the exact commit, but we started getting:
> The extension smart is not supported for docbook
Reading pandoc docs, I can't see what use to us "smart" could be
when writing the in-between docbook (to be converted to html).
https://pandoc.org/MANUAL.html#extension-smart
|
| | |\
| | |
| | | |
Fix dontRecurseIntoAttrs + add to lib + doc
|
| | | | |
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
crystal: use latest openssl
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
https://mail.haskell.org/pipermail/ghc-devs/2020-February/018643.html
|
| | |/ / |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | | |
doc/ociTools: exec is a shell builtin, not an external command
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| | |
As mentioned in #79975, the default on `legacyCargoFetcher` if left unspecified
is now `false`.
|
| |\ \
| | |
| | | |
doc: consistent formatting on python manual section
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
No material changes to docs, but trying to sanitize them for consistent
readability prior to looking at #75837.
- Use `*` for lists instead of `-`. I have no opinion one way or the other, but
the latter was only used in 1-2 places.
- Pad the code blocks with whitespace.
- Wrap to 80 characters, except for a few 1-liners that were only slightly over.
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
rxvt-unicode: rewrite plugin system
|
| | | | | | |
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | | |
I can't say I really understand that much about our cross stuff,
but this seems very clear.
|
| | |/ /
|/| | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When updating the section to python 3 some places still
referred to pythonPackages and were overlooked.
Decided to switch it to be more similar to the first
example binding pythonPackages and clarified comments a
bit based on confusion I observed on IRC.
Related to https://github.com/NixOS/nixpkgs/pull/77569
|
| | |
| |
| |
| |
| | |
We should not encourage installing build-tooling system-wide but
instead promote nix-shell.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Updating section about imperative use of ad-hoc virtual-environments for
use of pythons built-in `venv` module via venvShellHook. Also trying to
make it a bit friendlier to beginners by adding a bit more explanation
to the code snippet and some remarks old-school virtualenv.
Adjusting for venvShellHook and adding manual example
Adding pip install and replacing python2 example with python3
|
| | |
| |
| |
| |
| | |
This is a hook that loads a virtualenv from the specified `venvDir`
location. If the virtualenv does not exist, it is created.
|
| |\ \
| | |
| | | |
doc: Make callout marks & prompts unselectable
|
| | | |
| | |
| | |
| | | |
To make example copying easier.
|
| | | |
| | |
| | |
| | | |
Weirdly, no-one seems to have noticed this was broken.
|
| |\| | |
|
| | | |
| | |
| | |
| | | |
The example in the manual was out of date and didn't use the newer `pname`
convention, which simplifies the fetch call.
|
| |\| | |
|
| | | | |
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
doc : improve and cleanup of submitting-changes
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
nixpkgs manual: Update Haskell versions
|
| | | | | |
| | | | |
| | | | |
| | | | | |
and leave a comment in all-packages.nix that the docs should be updated
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is going to require more work.
This reverts commit 2dc4ab36772dfaf124af4d90e99c68038f46baa0.
|
| |\| | | |
| | | | |
| | | | |
| | | | | |
The nss rebuild isn't so small.
|
| | |/ / / |
|
| | | | | |
|