| 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 |
== Progress of this week == |
| 20 |
|
| 21 |
I've written a "many R packages -> Overlay" interface (OverlayCreator) |
| 22 |
which accepts R packages and organizes them in a queue. It also |
| 23 |
spawns/runs OverlayWorkers that try to create an ebuild for each |
| 24 |
package they get from the queue. Running several workers in parallel |
| 25 |
is possible. Successfully processed packages are then inserted into a |
| 26 |
portage tree-like structure that handles metadata creation and overlay |
| 27 |
writing to a directory, including ebuild/metadata.xml/Manifest files |
| 28 |
as well as the profiles dir (repo_name, categories, use.desc). |
| 29 |
All in all, creating an overlay for R packages is possible now. |
| 30 |
|
| 31 |
|
| 32 |
I'm on schedule. |
| 33 |
|
| 34 |
|
| 35 |
== Plans for the next week == |
| 36 |
|
| 37 |
I'll concentrate on remote syncing (CRAN, ...) 'cause I need them for |
| 38 |
testing soon (July) and it'll take some time to get the packages. |
| 39 |
|
| 40 |
-- |
| 41 |
Regards, |
| 42 |
André E. |
Archives