| 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'm on schedule: |
| 22 |
* wrote some documentation (man pages for the main script and |
| 23 |
repo/dependency rule files) |
| 24 |
* added "dependency types" to the resolver, it can now distinguish |
| 25 |
between internal (other R packages) and external deps (with some |
| 26 |
variations like "optional R package" - create ebuild even if dep |
| 27 |
cannot be resolved) |
| 28 |
|
| 29 |
== Plans for the next week == |
| 30 |
|
| 31 |
* redefine the timeline for the rest of the project |
| 32 |
* start with incremental overlay writing |
| 33 |
|
| 34 |
-- |
| 35 |
Regards, |
| 36 |
André E. |
Archives