This commit was created by a combination of scripts and tools:
- an ast-grep script to prefix things in meta with `lib.`,
- a modified nixf-diagnose / nixf combination to remove unused `with
lib;`, and
- regular nixfmt.
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
This reverts commit 65a333600d.
This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.
It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).
A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.
[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e458
The Go toolchain needed to build these is EOL, and comment says it doesn't want to be build with a newer toolchain, so removing these.
Signed-off-by: Paul Meyer <katexochen0@gmail.com>
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build a08b3a4d19.tar.gz \
--argstr baseRev b32a094368
result/bin/apply-formatting $NIXPKGS_PATH
My original commit was somewhat more tongue in cheek, but I think this
time I'm going to be honest, rather than hiding behind humor.
I'm angry that we as a community have reached a point where we're
falling apart because people would rather accept sealioning and bad
faith arguments that belong in a 2002 mailing list, not a 2024 software
community.
Every time I dare come back to the Nix community as a more active
contributor it feels like we have a fresh wave of controversy that we
don't ever heal from, everyone just moves on, more tired, and more
broken than before. And now it's crossed a line.
I'm out.
I hope the community decides to actually try and heal. Tolerating the intolerant
for too long has consequences - and the [paradox
of tolerance](https://en.wikipedia.org/wiki/Paradox_of_tolerance) has
come to its natural conclusion here.
If it does heal, I'll be back with a vengeance, because it turns out replacing
Nix is hard - emotionally and technically, and I'll miss it.
~Danielle
(this commit+PR are not a place for useless debates.)
Every time I decide to commit additional time to contributing to nix,
quite a few "concerned" members come out, either to decry a ban on
bigotry and fascism in 2021, or to declare support for minority groups
in Nix discriminatory, or a number of other incidents that are not worth
recounting in this leaving message.
To avoid any ambiguity, my reasoning is similar to pr306702, pr307033, and
several others who felt actively made unwelcome or outright harassed out
of the Nix project.
Please accept this letter as formal notice of my resignation from the
position of "Community Member" at DeterminateSystems.
Thank you for giving me the opportunity to work in this position - I
have thoroughly enjoyed being frustrated and saddened whenever
interacting with the DetSys community. However, I've decided it is time for me
to move on to another community that will hopefully be less tolerant of
willful hate and sexism.
~Danielle
Signed-off-by: Danielle Lancashire <dani@builds.terrible.systems>
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
