about summary refs log tree commit diff
path: root/pkgs/tools/misc/lorri
AgeCommit message (Collapse)AuthorFilesLines
2021-05-14lorri: 1.4.0 -> 1.5.0Guillaume Girol1-4/+4
2021-04-11lorri: 1.3.1 -> 1.4.0Bastian Köcher1-4/+4
2021-03-11lorri: 1.3.0 -> 1.3.1Profpatsch1-4/+4
Fix `lorri direnv` triggering an unconditional rebuild every time it is run. After fixing up the build loop people suddenly started noticing that lorri was evaluating every time something ran `lorri direnv`, which could potentially be every time the user switched between buffers in the editor. This is not the intended behaviour, since we should run an unconditional build only the first time the project is added to the watcher, and after rely on the watcher to notify us of any file changes (or the user running `lorri internal ping` to force a rebuild).
2021-03-06lorri: cleanup, formatSandro Jäckel1-16/+13
2021-03-05lorri: 1.2.0 -> 1.3.0Profpatsch1-6/+6
We forked lorri to nix-community, so this release also moves us over to the new official repository. Release notes: Fix the build loop. Previously, any change (for example a direnv ping or a change in the nix files) would add a new build invocation to the queue, and the builds would all be done one after the other. However, a new build will always use the newest state of the files anyway, so the CPU time spent on all the other builds will be wasted (and hog your processor). Now lorri will only finish the current build (if running) schedule at maximum one additional build if requested This should improve the resource use drastically in some situations. --- Make lorri daemon exit with exit code 0 instead of 130/143 on SIGINT or SIGTERM. --- Add lorri self-upgrade branch sub-subcommand. This enables us to point users to a branch name, in order to test out fixes from repository branches.
2021-01-15pkgs/tools: stdenv.lib -> libBen Siraphob1-1/+1
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch1-2/+2
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2020-09-09lorri: remove unnecessary output overrideProfpatsch1-3/+2
2020-08-04lorri: 1.1.1 -> 1.2.0Profpatsch1-7/+12
2020-07-29lorri: 1.1 -> 1.1.1Profpatsch1-6/+20
Patch release which adds a manpage. Adding a `man` and a `doc` output, and copying the files to the corresponding directories. The `overrideAttrs` is necessary because `buildRustPackage` does not allow adding outputs.
2020-06-30lorri: 1.0 -> 1.1Profpatsch1-7/+7
2020-02-27lorri: upgrade cargo fetcher and cargoSha256Benjamin Hipple1-4/+1
Infra upgrade as part of #79975; no functional change expected.
2020-02-13treewide: change fetchCargoTarball default to opt-outBenjamin Hipple1-0/+3
Changes the default fetcher in the Rust Platform to be the newer `fetchCargoTarball`, and changes every application using the current default to instead opt out. This commit does not change any hashes or cause any rebuilds. Once integrated, we will start deleting the opt-outs and recomputing hashes. See #79975 for details.
2020-02-05Revert "Revert "Merge master into staging-next""Frederik Rietdijk1-4/+4
In 87a19e9048773d5a363679617406ad148d36c3b8 I merged staging-next into master using the GitHub gui as intended. In ac241fb7a570d6cf81d229ad22a8889602639160 I merged master into staging-next for the next staging cycle, however, I accidentally pushed it to master. Thinking this may cause trouble, I reverted it in 0be87c79797a5fa384fbc356c74ed54f9f7829ea. This was however wrong, as it "removed" master. This reverts commit 0be87c79797a5fa384fbc356c74ed54f9f7829ea.
2020-02-05Revert "Merge master into staging-next"Frederik Rietdijk1-4/+4
I merged master into staging-next but accidentally pushed it to master. This should get us back to 87a19e9048773d5a363679617406ad148d36c3b8. This reverts commit ac241fb7a570d6cf81d229ad22a8889602639160, reversing changes made to 76a439239eb310d9ad76d998b34d5d3bc0e37acb.
2020-02-05lorri: unstable-2020-01-09 -> 1.0Leonhard Markert1-4/+4
2020-01-10lorri: unstable-2019-10-30 -> unstable-2020-01-09Leonhard Markert2-20/+25
`rustfmt` is now a compile time dependency because the varlink generated code is formatted with it.
2019-12-27lorri: remove cf-privateDaiderd Jordan1-2/+1
No longer needded since #63381.
2019-11-14lorri: init at version unstable-2019-10-30Leonhard Markert3-0/+126
Includes user service (nixos/modules/services/development/lorri) that starts on demand.