fetchFromGitLab: force re-fetch when rev changes (#14)

There are a few instances of `fetchFromGitLab` in the repo, for instance `gtk-doc.src`.

My primary goal when writing this was changing the output derivation following #11. This is doable with a lot less diff in `fetchFromGitLab`, but it's worth asking whether both fetchers should be different and why. I think a lot of the divergence comes from years of random commits rather than from design.

Reviewed-by: @isabelroses

Co-authored-by: Julie B. <no-reply@bbjubjub.fr>
Reviewed-on: #14
Co-authored-by: Ghost <>
Co-committed-by: Ghost <>

maintainers/maintainer-list.nix

@@ -1,68 +1,52 @@
-/* List of NixOS maintainers.
+/*
-    ```nix
+  List of Aux maintainers.
-    handle = {
+   ```nix
-      # Required
+   handle = {
-      name = "Your name";
+     # Required
+     name = "Your name";
+     forgejo = "forgejoUsername";
+     forgejoId = your-forgejo-id;
 
-      # Optional, but at least one of email, matrix or githubId must be given
+     # Optional, but at least one of email or matrix must be given
-      email = "address@example.org";
+     email = "address@example.org";
-      matrix = "@user:example.org";
+     matrix = "@user:example.org";
-      github = "GithubUsername";
-      githubId = your-github-id;
 
-      keys = [{
+     keys = [{
-        fingerprint = "AAAA BBBB CCCC DDDD EEEE  FFFF 0000 1111 2222 3333";
+       fingerprint = "AAAA BBBB CCCC DDDD EEEE  FFFF 0000 1111 2222 3333";
-      }];
+     }];
-    };
+   };
-    ```
+   ```
 
-    where
+   where
 
-    - `handle` is the handle you are going to use in nixpkgs expressions,
+   - `handle` is the handle you are going to use in nixpkgs expressions,
-    - `name` is a name that people would know and recognize you by,
+   - `name` is a name that people would know and recognize you by,
-    - `email` is your maintainer email address,
+   - `email` is your maintainer email address,
-    - `matrix` is your Matrix user ID,
+   - `matrix` is your Matrix user ID,
-    - `github` is your GitHub handle (as it appears in the URL of your profile page, `https://github.com/<userhandle>`),
+   - `forgejo` is your forgejo handle (as it appears in the URL of your profile page, `https://git.auxolotl.org/<userhandle>`),
-    - `githubId` is your GitHub user ID, which can be found at `https://api.github.com/users/<userhandle>`,
+   - `forgejoId` is your forgejo user ID, which can be found at `https://git.auxolotl.org/api/v1/users/<username>`,
-    - `keys` is a list of your PGP/GPG key fingerprints.
+   - `keys` is a list of your PGP/GPG key fingerprints.
 
-    Specifying a GitHub account ensures that you automatically:
+   `handle == forgejo` is strongly preferred whenever `forgejo` is an acceptable attribute name and is short and convenient.
-    - get invited to the @NixOS/nixpkgs-maintainers team ;
-    - once you are part of the @NixOS org, OfBorg will request you review
-      pull requests that modify a package for which you are a maintainer.
 
-    `handle == github` is strongly preferred whenever `github` is an acceptable attribute name and is short and convenient.
+   If `forgejo` begins with a numeral, `handle` should be prefixed with an underscore.
+   ```nix
+   _1example = {
+     forgejo = "1example";
+   };
+   ```
 
-    If `github` begins with a numeral, `handle` should be prefixed with an underscore.
+   Add PGP/GPG keys only if you actually use them to sign commits and/or mail.
-    ```nix
-    _1example = {
-      github = "1example";
-    };
-    ```
 
-    Add PGP/GPG keys only if you actually use them to sign commits and/or mail.
+   To get the required PGP/GPG values for a key run
+   ```shell
+   gpg --fingerprint <email> | head -n 2
+   ```
 
-    To get the required PGP/GPG values for a key run
+   !!! Note that PGP/GPG values stored here are for informational purposes only, don't use this file as a source of truth.
-    ```shell
-    gpg --fingerprint <email> | head -n 2
-    ```
 
-    !!! Note that PGP/GPG values stored here are for informational purposes only, don't use this file as a source of truth.
+   More fields may be added in the future, however, in order to comply with GDPR this file should stay as minimal as possible.
 
-    More fields may be added in the future, however, in order to comply with GDPR this file should stay as minimal as possible.
+   When editing this file, please ensure that you have added yourself in alphabetical order of your handle.
-
-    When editing this file:
-     * keep the list alphabetically sorted, check with:
-         nix-instantiate --eval maintainers/scripts/check-maintainers-sorted.nix
-     * test the validity of the format with:
-         nix-build lib/tests/maintainers.nix
-
-    See `./scripts/check-maintainer-github-handles.sh` for an example on how to work with this data.
-
-    When adding a new maintainer, be aware of the current commit conventions
-    documented at [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions)
-    file located in the root of the Nixpkgs repo.
 */
-{
+{ }
-
-}

pkgs/build-support/fetchgitlab/default.nix

@@ -2,7 +2,9 @@
 
 lib.makeOverridable (
 # gitlab example
-{ owner, repo, rev, protocol ? "https", domain ? "gitlab.com", name ? "source", group ? null
+{ owner, repo, rev, protocol ? "https", domain ? "gitlab.com", group ? null
+, pname ? lib.concatStringsSep "-" ([ "source" domain ] ++ (lib.optional (group != null) group) ++ [ owner repo ])
+, name ? "${pname}-${rev}"
 , fetchSubmodules ? false, leaveDotGit ? false
 , deepClone ? false, forceFetchGit ? false
 , sparseCheckout ? []

pkgs/build-support/fetchsavannah/default.nix

@@ -2,7 +2,7 @@
 
 lib.makeOverridable (
 # cgit example, snapshot support is optional in cgit
-{ repo, rev, name ? "source"
+{ repo, rev, name ? "source-savannah.gnu.org-${repo}-${rev}"
 , ... # For hash agility
 }@args: fetchzip ({
   inherit name;