unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: {bioinformatics,bioconductor}.scm cleaning?
Date: Wed, 11 Sep 2019 18:10:05 +0200	[thread overview]
Message-ID: <CAJ3okZ27o2xUT_aHX_pzo=e7o6HdEHvxw+qJvmtGKfrYx5_xQg@mail.gmail.com> (raw)

Dear,

Based on the (old) discussion [1] I would like to address this move.

[1] https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00266.html


However, there is already incoherence in bioconductor.scm. :-)


First, the commit c586f427b4 changes `bioconductor-uri` which now
takes optional package type. Thanks Ricardo. :-)
The use of `string-append` in the `uri` field--introduced because of
the annotation and experiment
package--is not expected, right?
Especially, they generally use ".../release/..." without a second
stable URI. Therefore, the future time travel will break.

What is the best: one patch correcting all the packages involved or
one patch per involved package?


Second, all the Bioconductor packages seem to be having a git uri
https://git.bioconductor.org/packages/<name>. And based on the new [2]
`guix lint -c archival` which automatically sends a request to
Software Heritage (SWH) when the fetching method is VCS, it appears to
me a good policy to fix the method to `git-fetch` in the file
`bioconductor.scm`. What do you think ?

From my knowledge, Bioconductor is not yet archived by them. But even
it will be, archive the source in SWH at the "lint time"--i.e., when
the package is modified in Guix--eases their work and ensures
robustness in time travel from our side. From my opinion, replace
`url-fetch` by `git-fetch` will be a good practise.

What do you think?

[2] https://lists.gnu.org/archive/html/guix-patches/2019-08/msg00580.html


Third, bioconductor.scm contains (3) packages which are not in
Bioconductor 3.9; (r-monocle3, r-cicero-monocle3, r-cistopic). Is it
expected?


All the best,
simon

                 reply	other threads:[~2019-09-11 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ27o2xUT_aHX_pzo=e7o6HdEHvxw+qJvmtGKfrYx5_xQg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).