Date: 2010-08-05 13:16
Sender: Henrik BengtssonIf the R-forge servers uses R_check_force_suggests=false (as CRAN servers do), then you could try to change your DESCRIPTION file to have use "Suggests: EBImage" instead of "Depends: EBImage". If you do this, you have to add an explicit
require("EBImage") || stop("Package not loaded: EBImage");
in your startup code or in the function(s) using EBImage.
This is a trick, but at least it should solve you R-forge problem. If/whenever EBImage is installed on R-forge, it doesn't take much to move back.
FYI, a long time ago, I also asked for EBImage to be on the R-forge servers. Installing EBImage is probably quite tedious. I don't think I got a reply. My solution was to add my own dummy/empty EBImage package to R-forge, cf. https://r-forge.r-project.org/R/?group_id=429.
I realize that this now may cause a problem for you, in the sense that you should get lots of NOTEs (not WARNINGs or ERRORs) that several functions you call are not defined. However, I'm surprised by your error message, because it indicates that not even this dummy package is detected. Have you checked if you get the same error message on the other R-forge machines?
Henrik B
|
