public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Auke Booij <auke@tulcod.com>
To: gentoo-science@lists.gentoo.org, brian.dolbec@gmail.com,
	"Sébastien Fabbro" <bicatali@gentoo.org>
Subject: [gentoo-science] G-CRAN works, testing needed
Date: Sat, 7 Aug 2010 19:00:22 +0200	[thread overview]
Message-ID: <AANLkTinuYEg+J9sLbztxRDr_O9GhnnwrjELnw8C+qPx3@mail.gmail.com> (raw)

Hi there, fellow scientists!

So I guess that if you haven't lived under a rock for the past few
months (and did not recently join gentoo-science), you have probably
heard about my efforts to help y'all install R extension packages
(CRAN and bioconductor are the obvious targets, since they are the
most popular R package repositories). My project is pretty much
complete now, and I'd like to tell you how to use my code and start
using R packages.

Now, I solved the problem slightly differently from packages like
g-cpan and g-octave. Instead of generating ebuilds as they are needed,
I've written another package called g-common which gives us
transparent access to non-ebuild package repositories (although
currently only R repos and PEAR are supported). To make our life even
easier, I've written a layman patch to be able to access R package
repositories just like we would access a regular ebuild overlay.

The code is not in portage yet, of course, so this is how you install,
as a simple example, the "zoo" package from CRAN:
-add the kuroo and science overlays if you don't have them yet
-install =layman-8888 from kuroo and g-cran from science (g-common is
currently included in g-cran)
-save the attached repositories.xml to /var/lib/repositories.xml (or
whatever you think is appropriate)
-edit /etc/layman/layman.cfg and add file:///var/lib/repositories.xml
to "overlays" (on its own line)
-layman -a CRAN
-emerge -av dev-R/zoo
For your convenience, I also added the bioconductor repositories to
repositories.xml. If you'd like to try these, please note that the
"annotation" part of bioconductor depends on the "bioc" part (and all
the gene databases and stuff are in "annotation", so you'll probably
want to get both).

Please test packages, and tell me about everything that you think
could be improved. Build errors, usability problems... tell me what
you think, so that we can make Gentoo the first distribution which can
directly install non-native packages using the package manager!

Should you have any questions or remarks, you can often find me on IRC
(#gentoo-soc, #gentoo-science, or just privmsg me), but I regularly
read my email too.
Auke Booij / tulcod.



             reply	other threads:[~2010-08-07 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 17:00 Auke Booij [this message]
2010-08-07 17:02 ` [gentoo-science] Re: G-CRAN works, testing needed Auke Booij

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=AANLkTinuYEg+J9sLbztxRDr_O9GhnnwrjELnw8C+qPx3@mail.gmail.com \
    --to=auke@tulcod.com \
    --cc=bicatali@gentoo.org \
    --cc=brian.dolbec@gmail.com \
    --cc=gentoo-science@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox