| 1 |
Hi everyone, |
| 2 |
|
| 3 |
== Brief summary of this project == |
| 4 |
|
| 5 |
This project is a continuation of last year's project, "Automatically |
| 6 |
generated overlay of R packages". Its aims are extending overlay |
| 7 |
creation and, more importantly, automated overlay maintenance. |
| 8 |
|
| 9 |
For reference, the roverlay git repo can be found at [0], which also |
| 10 |
provides some documentation [1]. |
| 11 |
|
| 12 |
|
| 13 |
== Last week's progress == |
| 14 |
|
| 15 |
* completed (code for) selfdep validation. Unresolvable, but optional |
| 16 |
selfdeps are now included in the MISSINGDEPS variable which is used to |
| 17 |
inform users about such dependencies during installation |
| 18 |
(pkg_postinst()). |
| 19 |
* produced ebuilds have a LICENSE variable now (if enough information |
| 20 |
available to create it) |
| 21 |
* added a faster Manifest creation that shares checksums with other |
| 22 |
roverlay modules (namely distmap) |
| 23 |
* some changes/additions to ease installation of roverlay on the server: |
| 24 |
-> config file generation via "roverlay-mkconfig" |
| 25 |
-> creation of essential dirs with proper permission via "roverlay setupdirs" |
| 26 |
These commands don't have to be run manually. Instead, the ebuild's |
| 27 |
pkg_config() (roverlay-9999.ebuild) asks a few questions and does |
| 28 |
everything necessary. So, "emerge <roverlay>" followed by "emerge |
| 29 |
--config <roverlay>" and the server is ready to run. |
| 30 |
|
| 31 |
Overall status: on schedule |
| 32 |
|
| 33 |
|
| 34 |
== Plans for this week == |
| 35 |
|
| 36 |
* get documentation up-to-date |
| 37 |
|
| 38 |
|
| 39 |
[0] http://git.overlays.gentoo.org/gitweb/?p=proj/R_overlay.git;a=summary |
| 40 |
[1] http://git.overlays.gentoo.org/gitweb/?p=proj/R_overlay.git;a=blob_plain;f=doc/html/usage.html;hb=HEAD |
| 41 |
|
| 42 |
Regards, |
| 43 |
André E. |
Archives