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-loomr.
Date: Thu, 10 Sep 2020 14:01:35 +0200	[thread overview]
Message-ID: <CAJ3okZ2d8rzWNHuG=MwpfyX6F2ws_PBsS-Df3MF+z4TaKUpc1w@mail.gmail.com> (raw)
In-Reply-To: <87k0x16hn2.fsf@elephly.net>

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

> > Where would I add a non-CRAN and non-Bioconductor package to?  Perhaps
> > this situation won't occur again, and should raise a flag, because I
> > think I've never had this case before.
>
> We don’t have any good place for those packages.  It would be good to
> have a dumping ground for packages like that, and for those that are on
> CRAN but unusually depend on Bioconductor packages.

IMHO, for non-CRAN and non-Bioconductor R packages, they should go to
thematic files: bioinformatics.scm or machine-learning.scm or
name-it.scm.

However, some dependency issues could happen, and e.g., CRAN package
could be in bioconductor.scm as r-deconstructsigs -- with a comment.

Last, should CRAN packages in statistics.scm go in cran..scm or not?


All the best,
simon


  reply	other threads:[~2020-09-10 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200909145626.7782.91114@vcs0.savannah.gnu.org>
2020-09-09 16:02 ` branch master updated: gnu: Add r-loomr Ricardo Wurmus
2020-09-10  9:13   ` Roel Janssen
2020-09-10 10:38     ` Ricardo Wurmus
2020-09-10 12:01       ` zimoun [this message]
2020-09-10 12:23         ` Ricardo Wurmus

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='CAJ3okZ2d8rzWNHuG=MwpfyX6F2ws_PBsS-Df3MF+z4TaKUpc1w@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).