(address . guix-patches@gnu.org)(name . Simon Tournier)(address . zimon.toutoune@gmail.com)
This format had been discussed in
* hydra/build-package-metadata.scm (origin->json)[resolve]: Add the keyword
'submodule' when the Git reference is recursive.
---
hydra/build-package-metadata.scm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
Hi,
This patch helps on SWH side.
Nevertheless, if it is possible from your side to add a new boolean field in
the JSON file (submodules ?) indicating that submodules should be fetched to
compute the hash, this will simplify the processing from our side.
Cheers,
simon
Toggle diff (20 lines)
diff --git a/hydra/build-package-metadata.scm b/hydra/build-package-metadata.scm
index 0a75204..9f90c5e 100755
--- a/hydra/build-package-metadata.scm
+++ b/hydra/build-package-metadata.scm
@@ -182,7 +182,10 @@ superseded packages."
"recursive"))))
'())
,@(if (eq? method git-fetch)
- `(("git_ref" . ,(git-reference-commit uri)))
+ `(("git_ref" . ,(git-reference-commit uri))
+ ,@(if (git-reference-recursive? uri)
+ '(("submodule" . "true"))
+ '()))
'())
,@(if (eq? method svn-fetch)
`(("svn_revision" . ,(svn-reference-revision uri)))
base-commit: 8f703892a6d549d52eb0374deb11d6af734065d4
--
2.38.1