| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | pkgs/shells: enable strictDeps | Artturin | 2022-05-06 | 1 | -0/+2 |
| * | treewide: with stdenv.lib; in meta -> with lib;•••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
| Profpatsch | 2021-01-11 | 1 | -2/+2 |
| * | treewide: Per RFC45, remove all unquoted URLs | Michael Reilly | 2020-04-10 | 1 | -1/+1 |
| * | treewide: update which packages I'm currently maintaining•••Idea shamelessly stolen from 4e60b0efae56cc8e1a8a606a5a89462c38aba305.
I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.
As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.
I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
| Maximilian Bosch | 2019-12-26 | 1 | -1/+1 |
| * | treewide: name -> pname (easy cases) (#66585)•••treewide replacement of
stdenv.mkDerivation rec {
name = "*-${version}";
version = "*";
to pname | volth | 2019-08-15 | 1 | -1/+1 |
| * | gradle-completion: 1.3.1 -> 1.4.1•••Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/gradle-completion/versions
| R. RyanTM | 2019-03-02 | 1 | -2/+2 |
| * | gradle-completion: init at 1.3.1 (#42929)•••This package adds completion scripts for `gradle` on the `bash` and
`zsh` shells.
The completions can be enabled like this:
```
{ pkgs, ... }:
{
environment.systemPackages = [ pkgs.gradle pkgs.gradle-completion ];
programs.zsh.enable = true;
}
```
The package stores the scripts into the expected directories in
`$out/share` to ensure that the shells can easily find their scripts.
Closes #42799 | Maximilian Bosch | 2018-07-05 | 1 | -0/+35 |
