public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "André Erdmann" <dywi@mailerd.de>
To: gentoo-soc@lists.gentoo.org
Cc: Denis Dupeyron <calchan@gentoo.org>
Subject: [gentoo-soc] Automatically generated overlay of R packages - progress report #7
Date: Mon, 9 Jul 2012 12:10:48 +0200	[thread overview]
Message-ID: <CAGrucu0iNjM_92C0heyzFAHcZdF3YBWNbN_SpvUi=ZiPet6KCg@mail.gmail.com> (raw)

Hi everyone,

== Brief summary of this project ==

The aim of this project is to create scripts that automate the process
of overlay creation/maintenance for R packages from repositories such
as CRAN and Bioconductor.

Longer:
For the ebuild creation of a single package one needs to extract the
package, copy-paste data from its description file to the ebuild and
look up dependencies, which is time-consuming.
Although trivial for a few number of packages, this is practically
impossible to do by hand for repositories like CRAN (> 3500 packages),
especially 'cause it also requires tracking changes (new / updated /
removed packages).
The solution is to automate that process and this is what this project is about.

== Progress of this week ==

First of all, I've written a a main script that is capable of running
sync and/or overlay creation. Running (testing) overlay creation for a
local directory with pre-downloaded packages is possible using
'./main.py --from <the package dir>'. Then, I've did some testing and
fixed issues like invalid tokens in metadata.xml and "`" in the
DESCRIPTION variable of ebuilds.
I've also written how to use the config files.

I'm on schedule.

== Plans for the next week ==

Document what I've written so far

-- 
Regards,
André E.



             reply	other threads:[~2012-07-09 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 10:10 André Erdmann [this message]
2012-07-10  3:47 ` [gentoo-soc] Automatically generated overlay of R packages - progress report #7 heroxbd
2012-07-10  7:43   ` André Erdmann

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='CAGrucu0iNjM_92C0heyzFAHcZdF3YBWNbN_SpvUi=ZiPet6KCg@mail.gmail.com' \
    --to=dywi@mailerd.de \
    --cc=calchan@gentoo.org \
    --cc=gentoo-soc@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