| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | libglycin-gtk4: init (split out of libglycin) (#481377) | Jan Tojnar | 2026-02-04 | 1 | -0/+24 |
| |\ |
|
| | * | libglycin: Introduce setup hook for adding loader paths to wrapper•••This setup hook discovers glycin loaders in the inputs list it is placed into, and adds them to `gappsWrapperArgs`. This should simplify glycin-dependent programs’ expressions.
Just add `libglycin.setupHook` (for Rust programs) or `libglycin` (for other languages) to `buildInputs`. The latter will also pull in the setup hook.
Note, the setup hook needs to go to the `buildInputs` since we cannot have a different offset when used as standalone hook instead of propagated from `libglycin`. We chose `hostOffset` to make it work with the proper placement of `libglycin` in `buildInputs`.
Co-authored-by: Seth Flynn <getchoo@tuta.io>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
| Leah Amelia Chen | 2026-01-19 | 1 | -0/+9 |
| | * | libglycin: Add setup hook for patching Rust vendor directory•••Glycin rust library searches `bwrap` on path. This would require every reverse dependency to add `bubblewrap` to its `PATH`, which would be quite annoying to ensure. Especially when libraries start using glycin.
We provide `passthru.glycinPathsPatch` to perform source-level hardcoding but that doesn't work with apps that use `rustPlatform.cargoSetupHook` since it assumes a setup where snapshots of GNOME sources already contain vendored Rust dependencies under `vendor/`.
The setup hook instead provides a much more flexible approach that uses the `$cargoDepsCopy` variable provided by `cargoSetupHook`, which points to the local, modifiable copy of Cargo dependencies, to patch `src/sandbox.rs` just like `glycinPathsPatch`. If `$cargoDepsCopy` is not found, then the old behavior is used where Cargo dependencies are assumed to be under `vendor/`.
Additionally, the patch requires modifying `Cargo.lock` when using `rustPlatform.fetchCargoVendor`. The setup hook fixes that as well.
Rust programs just need to add `libglycin.patchVendorHook` and it should take care of this.
Co-authored-by: Seth Flynn <getchoo@tuta.io>
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
| Leah Amelia Chen | 2026-01-18 | 1 | -0/+15 |
| * | | doc/tauri: document hook dontTauriFixup | Stefan Nuernberger | 2026-02-01 | 1 | -0/+3 |
| * | | docs: remove references to the xorg namespace (#479692) | Jo | 2026-01-26 | 1 | -16/+6 |
| |\ \ |
|
| | * | | docs: remove references to the xorg namespace | quantenzitrone | 2026-01-23 | 1 | -16/+6 |
| | |/ |
|
| * / | Rocq: Update documentation | Pierre Roux | 2026-01-26 | 1 | -7/+14 |
| |/ |
|
| * | coqPackages: add coqWithPackages/coqWithPackages' functions (#444257) | Théo Zimmermann | 2026-01-16 | 1 | -0/+6 |
| |\ |
|
| | * | coqPackages: add coqWithPackages/coqWithPackages' functions | Tom McLaughlin | 2026-01-13 | 1 | -0/+6 |
| * | | fetchFromSavannah: deprecate•••The Savannah administrators do not want package maintainers to use
cgit snapshots due to putting strain on the servers and have disabled
cgit snapshots for most if not all of their repositories.
See: https://lists.gnu.org/archive/html/savannah-hackers/2025-12/msg00014.html
Co-authored-by: Philip Taron <philip.taron@gmail.com>
Co-authored-by: LIN, Jian <me@linj.tech>
| Jasi | 2026-01-14 | 1 | -4/+2 |
| |/ |
|
| * | zig: use setupHook attribute on zig derivation•••By moving the zig setup hook to the zig derivation itself, we allow for
zig to splice correctly with `callPackage`, meaning that the correct zig
can be pulled in during builds when zig is in `nativeBuildInputs` (for
example).
This change retains the `zig.hook` attribute for backward compatibility
by just pointing to the zig derivation. This also removes
`zig_default_flags`, since now the setup hook is not a derivation that
can be overridden. Overriding the build flags can now be done by setting
`dontSetZigDefaultFlags = true`.
| Jared Baur | 2026-01-09 | 1 | -6/+15 |
| * | doc/linux: make it explicit that we do not accept new kernel flavors (#473318) | Maximilian Bosch | 2025-12-29 | 1 | -0/+3 |
| |\ |
|
| | * | doc/linux: make it explicit that we do not accept new kernel flavors•••So far, this rule was only a comment in the `linux-kernels.nix`[1],
better make it explicit in our manual.
[1] https://github.com/NixOS/nixpkgs/blob/f74c64bacf35f0be2c781de68afc2c84a8c54ea1/pkgs/top-level/linux-kernels.nix#L91
| Maximilian Bosch | 2025-12-22 | 1 | -0/+3 |
| * | | doc/stdenv: add a note about `strictDeps` | Tobias Mayer | 2025-12-26 | 1 | -0/+3 |
| |/ |
|
| * | doc: collapse old contributing sections to one redirect•••also link from nixos/doc to the in-tree README directly
| Valentin Gagarin | 2025-12-15 | 1 | -6/+2 |
| * | doc/javascript: move nodePackages information back to README.md•••Adding new packages here is discouraged, for reasons enumerated in
https://github.com/NixOS/nixpkgs/issues/229475, so let's move this
(mostly developer-facing) documentation back into its original location
in pkgs/development/node-packages/README.md.
| Tomodachi94 | 2025-11-29 | 1 | -9/+0 |
| * | 26.05 Documentation | jopejoe1 | 2025-11-24 | 1 | -0/+24 |
| * | Merge master into staging-next | nixpkgs-ci[bot] | 2025-11-07 | 1 | -0/+18 |
| |\ |
|
| | * | doc: update platform support (#401821) | Tristan Ross | 2025-11-07 | 1 | -0/+18 |
| | |\ |
|
| | | * | doc: update platform support | Tristan Ross | 2025-07-29 | 1 | -0/+18 |
| * | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-10-28 | 1 | -7/+2 |
| |\| | |
|
| | * | | cudaPackages: build redists from manifests and add CUDA 13 (#437723) | Connor Baker | 2025-10-27 | 1 | -7/+2 |
| | |\ \ |
|
| | | * | | doc: update CUDA section•••Signed-off-by: Connor Baker <ConnorBaker01@gmail.com>
| Connor Baker | 2025-10-22 | 1 | -7/+2 |
| * | | | | Merge remote-tracking branch 'origin/staging-next' into staging | K900 | 2025-10-25 | 1 | -0/+3 |
| |\| | | |
|
| | * | | | doc: document buildPython* stdenv overriding via <function>.override | Yueh-Shun Li | 2025-10-23 | 1 | -0/+3 |
| | |/ / |
|
| * | | | Merge remote-tracking branch 'origin/staging-next' into staging | K900 | 2025-10-22 | 1 | -0/+36 |
| |\| | |
|
| | * | | julec.hook: init•••Co-authored-by: philiptaron <philip.taron@gmail.com>
| adam | 2025-10-22 | 1 | -0/+36 |
| * | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-10-20 | 1 | -12/+3 |
| |\| | |
|
| | * | | doc/cmake: document cmakeBuildType (#442334) | Sebastián Mancilla | 2025-10-19 | 1 | -0/+3 |
| | |\ \ |
|
| | | * | | doc/cmake: document cmakeBuildType | Grimmauld | 2025-09-12 | 1 | -0/+3 |
| | * | | | Revert "stdenv: pURL implementation (#421125)"•••This reverts commit 54271156702fc3a3f5d156df567a2a4a274bac6b, reversing
changes made to 88ee2ac331edc3ce9f9df92aaf824592473ed868.
| d068328 | 2025-10-18 | 1 | -12/+0 |
| * | | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-10-18 | 1 | -0/+3 |
| |\| | | |
|
| | * | | | nrfutil: 7.13.0 -> 8.1.1, package all installables (#440671) | h7x4 | 2025-10-18 | 1 | -0/+3 |
| | |\ \ \ |
|
| | | * | | | nrfutil: 7.13.0 -> 8.1.1, package all installables•••This commit introduces a `withExtensions` function, to allow for
downloading and using the other installable parts of nrfutil.
It also introduces support for aarch64-linux, as well as updating the
program.
| h7x4 | 2025-10-16 | 1 | -0/+3 |
| * | | | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-10-17 | 1 | -0/+12 |
| |\| | | | |
|
| | * | | | | stdenv: pURL implementation (#421125) | Arian van Putten | 2025-10-17 | 1 | -0/+12 |
| | |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | * | | | stdenv: pURL docu enhancements & list interface | Hans Joachim Kliemeck | 2025-10-03 | 1 | -0/+3 |
| | | * | | | stdenv: pURL implementation | h0nIg | 2025-10-03 | 1 | -0/+9 |
| * | | | | | cc-wrapper: make availability warnings into errors (#445119) | Randy Eckenrode | 2025-10-09 | 1 | -0/+3 |
| |\ \ \ \ \ |
|
| | * | | | | | doc/stdenv/platform-notes: add section about availability checks | Randy Eckenrode | 2025-09-29 | 1 | -0/+3 |
| * | | | | | | cc-wrapper: add support for libcxxhardeningfast/extensive hardening flags•••as with glibcxxassertions, we don't yet have a nice mechanism
for deferring support decisions to the c++ library in use, so
for now at least enabling this hardening flag will cause
_LIBCPP_HARDENING_MODE to be defined on all compilers
| Robert Scott | 2025-10-08 | 1 | -0/+6 |
| * | | | | | | {cc-wrapper,bintools-wrapper}: drop pie hardening flag (#442510) | Philip Taron | 2025-10-07 | 1 | -4/+2 |
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
|
| | * | | | | | doc: drop pie flag from sec-hardening-in-nixpkgs | Luna Nova | 2025-09-30 | 1 | -4/+2 |
| | |/ / / / |
|
| * | | | | | linux: new workflow for kernel changes (#444973) | Wolfgang Walther | 2025-10-06 | 1 | -0/+9 |
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | * | | | | linux: new workflow for kernel changes•••See https://github.com/NixOS/nixpkgs/issues/437208#issuecomment-3288623669
Depends on https://github.com/NixOS/org/pull/172
As documented below, the idea is to essentially group all changes
rebuilding all VM tests with kernel updates and merge them together into
`master` whenever the Linux kernels get updated.
This documents the workflow of updates in the nixpkgs manual. While at
it, I removed the README from the packages because
* it's horribly outdated
* I didn't even know it exists which confirms that its discoverability
was very poor
and added the relevant portions into the nixpkgs manual as well.
| Maximilian Bosch | 2025-10-05 | 1 | -0/+9 |
| | |/ / / |
|
| * | | | | Merge master into staging-next | nixpkgs-ci[bot] | 2025-09-28 | 1 | -28/+10 |
| |\ \ \ \ |
|
| | * \ \ \ | treewide: remove bower (#443594) | Sandro | 2025-09-28 | 1 | -28/+10 |
| | |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | * | | | treewide: remove bower | Sandro Jäckel | 2025-09-26 | 1 | -28/+10 |
| | | |/ / |
|
| * | / / | doc/stdenv/platform-notes: add section about libc++ | Randy Eckenrode | 2025-09-15 | 1 | -0/+6 |
| |/ / / |
|
| * / / | Reapply "stdenv: Add CPE fields to meta"•••This reverts commit de74f9caf0854a9ee8c39774cf4521870fa1f44a.
| Yuriy Taraday | 2025-09-15 | 1 | -0/+15 |
| |/ / |
|
