Commit graph

4 commits

Author SHA1 Message Date
Maximilian Bosch
9842c4b107
treewide: update which packages I'm currently maintaining
Idea shamelessly stolen from 4e60b0efae.

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.
2019-12-26 15:27:47 +01:00
volth
46420bbaa3 treewide: name -> pname (easy cases) (#66585)
treewide replacement of

stdenv.mkDerivation rec {
  name = "*-${version}";
  version = "*";

to pname
2019-08-15 13:41:18 +01:00
R. RyanTM
3b51bceee6 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
2019-03-02 03:02:50 -08:00
Maximilian Bosch
4dfea241bc 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
2018-07-05 00:34:28 +02:00