1 |
Hello 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 it's 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 |
|
20 |
== Progress of this week == |
21 |
|
22 |
I'm almost on schedule now: |
23 |
|
24 |
* added logging to the modules |
25 |
* a config module that is able to load R package description field |
26 |
definitions, e.g. 'Depends' alias 'Depend', marking a field as |
27 |
mandatory, specifying a default value for a field,... . Other parts of |
28 |
this module (main config, dependency rules) are still todo. |
29 |
* a functioning R package -> ebuild conversion: an EbuildCreator |
30 |
accepts R packages and organizes them as jobs (EbuildJob) in a |
31 |
queue/list, which is (later) a good entry point for threading. |
32 |
|
33 |
== Plans for the next week == |
34 |
|
35 |
My plan for this week is to get to complete the config module and then |
36 |
start with adding dependency resolution to the ebuild creation. |
37 |
|
38 |
|
39 |
-- |
40 |
Regards, |
41 |
André E. |