[pkg-bioc] State of BioC compilations

Dirk Eddelbuettel edd at debian.org
Sun Feb 11 19:34:31 CET 2007


On 11 February 2007 at 19:11, Steffen Moeller wrote:
| > Ahhh :)  In which case I shall be starting over.
| It is more like "araaarrghhh!" But only those packages for which I did the 

Yes.   I would actually like to test whether CVS+wiki are self-sufficient to
launch a new (local) build. Given how I have been unable to do one since
Friday, I would have to say no.

As for R-devel and Bioc-devel, I'd say no.  IMHO it is easier to work on the
_current_ bioc with the _current_ R binary in unstable.

| > [ We should also put the script(s) you have there into CVS, no ? ]
| There are no scripts, really, just some lines to execute from the Wiki. 

The one I refer is a shell script from the wiki that had a syntax error. It
is easier to test and amend if these are in the CVS too.

| > And didn't Andrew try that R-Depends analysis this summer for the CRAN
| > part? Isn;t that why we now need SQLite?
| I have not grasped yet what to expect from the SQLite bits.

Stateful information [ what packages are there, what versions have we
package, what versions changed, ... ] can be stored in a db. SQLite is easy
as it is a file, and it can be read from/written to easily with R, Perl,
Python, ...

Dirk

-- 
Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison



More information about the pkg-bioc-devel mailing list