Gentoo Archives: gentoo-soc

From: "André Erdmann" <dywi@×××××××.de>
To: gentoo-soc@l.g.o
Cc: Denis Dupeyron <calchan@g.o>
Subject: [gentoo-soc] Automatically generated overlay of R packages - progress report #10
Date: Tue, 31 Jul 2012 09:06:08
Message-Id: CAGrucu26=UBxYK7tci=0v75YFAPkoe5kixri5JeEm7_3dZ53Hw@mail.gmail.com
1 Hi everyone,
2
3 == Brief summary of this project ==
4
5 The aim of this project is to create scripts that automate the process
6 of overlay creation/maintenance for R packages from repositories such
7 as CRAN and Bioconductor.
8
9 Longer:
10 For the ebuild creation of a single package one needs to extract the
11 package, copy-paste data from its description file to the ebuild and
12 look up dependencies, which is time-consuming.
13 Although trivial for a few number of packages, this is practically
14 impossible to do by hand for repositories like CRAN (> 3500 packages),
15 especially 'cause it also requires tracking changes (new / updated /
16 removed packages).
17 The solution is to automate that process and this is what this project is about.
18
19 == Last week's progress ==
20
21 * Implemented incremental overlay writing: creation of an ebuild can
22 now be skipped if it already exists and added the possibility to keep
23 only the n-th latest ebuilds per package
24
25 * the overlay module can now be used for dependency resolution: all
26 added/existing packages are part of a DynamicSelfdepPool that resolves
27 package-deps (e.g. 'seewave' -> 'sci-R/seewave') without any
28 dependency rule file
29
30 * some minor changes based on test results (typos, corner cases like a
31 few Z compressed packages, ...)
32
33 * useful dependency rules: the last test run showed 30094/30921
34 successful ebuild creations (BIOC, CRAN, CRAN-Archive) with ~400
35 unresolvable dependencies. Most of them are from the 'Suggests' field
36 of a package for which ebuild creation ignores unresolvable deps
37 ("collect as many suggestions as possible"). Some are packages from
38 other repos (omegahat, R-Forge and packages without a repo) and some
39 are not in the portage tree (e.g. Cytoscape).
40
41
42 == Plans for this week ==
43
44 * implement another way to get packages (via http, with the option to
45 read/parse a remote's PACKAGES file to generate a package list)
46 * testing
47
48 --
49 Regards,
50 André E.