Commit graph

7 commits

Author SHA1 Message Date
Ghost 8be7956fc0 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 <>
2024-07-01 16:24:13 +00:00
Julie Tyché Bettens 9ed579059e fetchFromSavannah: force re-fetch when rev changes 2024-05-22 23:01:26 +10:00
Julie Tyché Bettens 7ec6274c37 fetchFromGitHub: use instance URL in name 2024-05-21 11:15:52 +05:30
Yueh-Shun Li d60eb7471e fetchgit: takes passthru argument 2024-05-21 11:15:52 +05:30
Yueh-Shun Li ef1e2ef8c2 fetchFromGitHub: take passthru and enhance overriding
Take optional argument `passthru` for custom passthru attribute set.

Update the `meta` attribute via `<pkg>.overrideAttrs` instead of
attribute set update (`//`).

Attach attributes `owner`, `repo` and `rev` via `passthru` instead of
attribute set update.
2024-05-21 11:15:52 +05:30
Yueh-Shun Li ff4126b6ba fetchFromGitHub: force re-fetch when rev changes
Prefix the default value of `name` with `rev` to force re-fetch
everytime `rev` changes.
2024-05-21 11:15:52 +05:30
Victor Fuentes 072e19ee33
pkgs: init 2024-05-13 11:34:52 -04:00