> 1) Get a list of recommended packages from that version of R - > preferably in a way that does not require them to be hard-coded in a > test script, but generated by R.
Unfortunately, I couldn't find one when I was looking for it. It might be worth asking the R list whether there is something like this that does not require Internet (which, after all, should not be a requirement for building Sage once one actually has a Sage copy), nor parsing some huge list of *all* packages. Ben's way of testing them should work (see http://cran.r-project.org/doc/manuals/R-admin.html, and he is right that library('tools') is needed), but I don't know how to get a shell script like spkg-check to run these commands in R, or anything else. Of course, this would do a lot more than check their presence, and would be more or less like running spkg-check, I guess. > 2) Test if all those recommended packages have actually built. > > Does that sound reasonable? If so, I'll try to sort out how to do it, > though any help would be appreciated, as I've never written any sort > of test in Sage, and I have never used R. But I see this as pretty > important, so will put some time in. > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
