unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>, guix-commits@gnu.org
Subject: Re: branch master updated: gnu: Add r-bisquerna.
Date: Thu, 10 Sep 2020 13:49:49 +0200	[thread overview]
Message-ID: <CAJ3okZ3c-4Egnak+hy+hQSkdAMpKGCw1J7VAEBF1=LWt8khF5A@mail.gmail.com> (raw)
In-Reply-To: <87blid6f72.fsf@elephly.net>

On Thu, 10 Sep 2020 at 13:30, Ricardo Wurmus <rekado@elephly.net> wrote:

> > It seemed so "bioinformatics"-specific.  But you're right, it's a CRAN
> > package, so that may be a better fit.  Shall I move it to CRAN?
>
> If you have time to do that, yes please.  Some time ago I started a
> half-hearted migration of R packages from (gnu packages bioinformatics)
> to (gnu packages cran) and (gnu packages bioconductor).  It’s not
> supremely important, but I think in the long term we’d like to have CRAN
> things in (gnu packages cran) and Bioconductor things in (gnu packages
> bioconductor), because it’s deliciously unsurprising. :)

I agree.  And it is also on my TODO but the Copyright lines lead to a
boring task. :-)

Does it make sense to add a subsection to:
https://guix.gnu.org/manual/devel/en/guix.html#Packaging-Guidelines
about R packages?

Cheers,
simon


  reply	other threads:[~2020-09-10 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200909150314.13619.80121@vcs0.savannah.gnu.org>
2020-09-09 16:04 ` branch master updated: gnu: Add r-bisquerna Ricardo Wurmus
2020-09-10 10:48   ` Roel Janssen
2020-09-10 11:31     ` Ricardo Wurmus
2020-09-10 11:49       ` zimoun [this message]
2020-09-10 12:33         ` Ricardo Wurmus
2020-09-10 14:43       ` Roel Janssen
2020-09-11 18:13         ` zimoun

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='CAJ3okZ3c-4Egnak+hy+hQSkdAMpKGCw1J7VAEBF1=LWt8khF5A@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-commits@gnu.org \
    --cc=guix-devel@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 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).