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: auxolotl/core#14
Co-authored-by: Ghost <>
Co-committed-by: Ghost <>
This commit is contained in:
Ghost 2024-07-01 16:24:13 +00:00 committed by isabel roses
parent c13b60bc67
commit 8be7956fc0

View file

@ -2,7 +2,9 @@
lib.makeOverridable ( lib.makeOverridable (
# gitlab example # 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 , fetchSubmodules ? false, leaveDotGit ? false
, deepClone ? false, forceFetchGit ? false , deepClone ? false, forceFetchGit ? false
, sparseCheckout ? [] , sparseCheckout ? []