From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 54787@debbugs.gnu.org
Subject: bug#54787: importer Bioconductor: no tarball, only Git
Date: Thu, 14 Apr 2022 17:03:37 +0200 [thread overview]
Message-ID: <868rs7zoza.fsf@gmail.com> (raw)
In-Reply-To: <87k0brvk73.fsf@elephly.net>
On Thu, 14 Apr 2022 at 15:57, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> On Thu, 14 Apr 2022 at 13:43, Ricardo Wurmus <rekado@elephly.net> wrote:
>>
>>> We probably should *not* use RELEASE_3_14 (or whatever) as the commit,
>>> though, because that is a moving target. We need to resolve to the
>>> actual commit and use its hash.
[...]
>> Do we follow ’master’? Is it a mirror of what Bioconductor names their
>> 3.14 release?
>
> We should not follow “master”. That’s the development branch. We
> should follow the current release branch.
To be sure to well understand you, you point is to have something like:
--8<---------------cut here---------------start------------->8---
(define* (bioconductor-git-reference name #:key commit)
(git-reference
(url (string-append %bioconductor-git-url name))
(commit commit))))
--8<---------------cut here---------------end--------------->8---
with an explicit commit for each package definition, right?
> Doesn’t Guile-Git support shallow clones? In any case, this should not
> be an obstacle for us. Ensuring long-term reproducibility is more
> important than space savings.
No, since libgit2 does not support it, IIUC.
<https://github.com/libgit2/libgit2/issues/3058>
Cheers,
simon
next prev parent reply other threads:[~2022-04-14 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 11:48 bug#54787: importer Bioconductor: no tarball, only Git zimoun
2022-04-11 16:15 ` Ricardo Wurmus
2022-04-12 16:25 ` zimoun
2022-04-14 11:43 ` Ricardo Wurmus
2022-04-14 12:59 ` zimoun
2022-04-14 13:57 ` Ricardo Wurmus
2022-04-14 15:03 ` zimoun [this message]
2022-04-14 14:04 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868rs7zoza.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54787@debbugs.gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.