Re: [Rd] CRAN policies

2012-03-30 Thread Matthew Dowle
csiro.au> writes: > There must be over 2000 people who have written CRAN packages by now; every extra > check and non-back-compatible additional requirement runs the risk of generating false-negatives and > incurring many extra person-hours to "fix" non-problems. Plus someone needs to document

Re: [Rd] --as-cran / BuildVignettes: false

2012-03-30 Thread Claudia Beleites
Paul, > I have packages where I know CRAN and other test platforms do not have > all the resources to build the vignettes, for example, access to > databases. For some of my vignettes that is true, too. For those, the vignette directory contains the .pdf produced on my machine and a "fake" .Rnw,

Re: [Rd] CRAN policies

2012-03-30 Thread Claudia Beleites
Paul, > One of the things I have noticed with the R 2.15.0 RC and --as-cran is > that the I have to bump the version number of the working copy of my [snip] > > I am curious how other developers approach this. Regardless of --as-cran I find it very useful to use the date as minor part of the v

[Rd] R-forge --as-cran

2012-03-30 Thread Paul Gilbert
(Renamed from "Re: [Rd] CRAN policies" because the of the muli-threading of that subject.) Claudia Actually, my version numbers are year-month dates, eg 2012.3-1, although I don't set them automatically. I have had some additional off-line discussion on this. The problem is this: Now when

Re: [Rd] CRAN policies

2012-03-30 Thread William Dunlap
It looks like you define a few functions that use substitute() or sys.call() or similar functions to look at the unevaluated argument list. E.g., "cq" <- function( ...) { # Saves putting in quotes! # E.G.: quoted( first, second, third) is the same as c( 'first', 'second', 'third') # wr

Re: [Rd] CRAN policies

2012-03-30 Thread Kevin Wright
I'll echo Mark's concerns. R _used_ to be a language for "turning ideas into software quickly". Now it is more like "prototyping ideas in software quickly", and then spend a substantial amount of time trying to follow administrative rules to package the code. Quality has its costs. Many of the

Re: [Rd] CRAN policies

2012-03-30 Thread Joshua Wiley
On Fri, Mar 30, 2012 at 11:41 AM, Kevin Wright wrote: > I'll echo Mark's concerns.  R _used_ to be a language for "turning ideas > into software quickly".  Now it is more like "prototyping ideas in software > quickly", and then spend a substantial amount of time trying to follow > administrative r

[Rd] RSiteSearch

2012-03-30 Thread Jonathan Baron
I don't know what the RSiteSearch function does anymore, or who maintains it. Please ignore this if you have nothing to do with it. I recently moved my R site, finzi.psych.upenn.edu to a new computer. Somehow some of the mailing-list search capabilities were lost, and I do not have time to find th

Re: [Rd] r-forge build failure bafflement

2012-03-30 Thread Ben Bolker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Figured it out (I think: I haven't gotten through restructuring and testing, but I think it's going to work now). I was paying insufficient attention to the build arguments, in particular - --resave-data=best. I previously had the clever idea to

Re: [Rd] r-forge build failure bafflement

2012-03-30 Thread Ben Bolker
On 12-03-30 08:14 PM, Brian G. Peterson wrote: > On my phone, so replying off-list, but wouldn't loading the data > objects in a running R session and using the appropriate > compression arguments to save() do the trick? - Brian I might try that, but I have a strong suspicion that R will try to