| 1 |
This week, I finalized G-CRAN's remote repository reading capabilities |
| 2 |
and prepared some code for building packages. As mentioned in last |
| 3 |
week's report, rfc822 is now being used to read a file called PACKAGES |
| 4 |
which contains a list of all packages in a CRAN-style repository. |
| 5 |
|
| 6 |
Bicatali kindly asked around how my git repository was doing, and a |
| 7 |
few minutes later I was in possession of my very own git repository, |
| 8 |
which you can find and track at [0]. |
| 9 |
|
| 10 |
If you want to play around with the current code a bit, clone the git |
| 11 |
repo and try the following: |
| 12 |
# mkdir /usr/local/cran |
| 13 |
# ./g-cran.py /usr/local/cran sync http://cran.r-project.org/ |
| 14 |
# ./g-cran.py /usr/local/cran list-packages |
| 15 |
# ./g-cran.py /usr/local/cran package x12 |
| 16 |
This creates a new overlay in /usr/local/cran (currently unpopulated; |
| 17 |
this is presumably something g-common will be responsible for) and |
| 18 |
syncs it from [1] (equally, you can pick any of your favorite CRAN |
| 19 |
mirrors). Then it lists all packages available and finally gives |
| 20 |
detailed information about the "x12" package. Some variables are set |
| 21 |
correctly, some don't conform exactly to PMS (the LICENSE variable is |
| 22 |
a great example of this) and some can be filled up later (and a few |
| 23 |
have to be statically set because the repository doesn't give any |
| 24 |
information about them). |
| 25 |
|
| 26 |
Up next week is being able to build packages. I wrote a couple of |
| 27 |
function definitions, but nothing's working yet. I should be able to |
| 28 |
issue a system() call to R CMD INSTALL cran-style packages. |
| 29 |
|
| 30 |
[0] http://git.overlays.gentoo.org/gitweb/?p=proj/g-cran.git;a=summary |
Archives