Re: [Rd] Standardizing included packages

2011-11-30 Thread peter dalgaard
On Dec 1, 2011, at 01:56 , Gabor Grothendieck wrote: > It seems that R is mostly distributed with the tcltk package but not always. > > Is there some reason for this inconsistency? Well, the tcltk package as such is part of the _source_ distribution of R. We have no centralized control over wh

[Rd] Standardizing included packages

2011-11-30 Thread Gabor Grothendieck
It seems that R is mostly distributed with the tcltk package but not always. Is there some reason for this inconsistency? It would be nice if one could count on those packages that are distributed on the Windows version of R being distributed on all other platforms too. -- Statistics & Software

Re: [Rd] Holding back on source code

2011-11-30 Thread Jordi GutiƩrrez Hermoso
On 28 November 2011 22:37, Sachinthaka Abeywardana wrote: > What I want to do is release the code and implement the package, and not > get in trouble considering I was with CSIRO when I did it. I am not an internet protocol lawyer, etc... Did you sign a contract that says the work you did under

Re: [Rd] sma installation error

2011-11-30 Thread Henrik Bengtsson
The sma package is deprecated since many years... ...however, by request from collaborators last year, I recompiled it to fix that error you are mention (see below). I just added a namespace (required in R 2.14.0). You can download it from: http://braju.com/R/repos/sma_0.5.17.tar.gz http://

[Rd] sma installation error

2011-11-30 Thread Justin
I tried different versions of sma**.tar.gz file either with "R CMD INSTALL -l packagepath sma**.tar.gz", "R INSTALL -l path sma**.tar.gz" and under R windows by "install.packages("sma_0.5.15.tar.gz",repos=NULL)" . I got same error == * installing *source* package 'sma' ... ** Creating de

[Rd] Bug in URLencode?

2011-11-30 Thread Hadley Wickham
Hi all, I think I've spotted a small bug in URLencode: + is not listed as a reserved character (and hence not percent encoded) even though it is listed as a reserved character in rfc3986 (http://tools.ietf.org/html/rfc3986#section-2.2). The documentation for URLencode cites rfc1738, which rfc3986