Re: [R-pkg-devel] Problem enhancing a package with a predict method not declared to be an S3 method

2017-12-17 Thread Chris Brien
Hi Duncan, Thanks for your comments. I appreciate that you do not speak for CRAN. I had thought that, while I am accessing asreml internals, I do not believe that it is the intention of the maintainer that they be internal. Indeed, I am only calling functions documented in the manual and so

Re: [R-pkg-devel] Lapack: undefined symbol: zgbsv_

2017-12-17 Thread Dirk Eddelbuettel
On 17 December 2017 at 17:50, Dirk Eddelbuettel wrote: | In short, but relying on (Rcpp)Armadillo, you are submit to it changing its That should have read: "... by relying on (Rcpp)Armadillo, you are subject to ..." My bad. | solver and it seems to have done so recently. And as R is

[Rd] Dialect for shell scripts

2017-12-17 Thread Rodrigo Tobar
Dear all, During a recent package submission, we were highlighted that some lines in our configure script didn't follow the correct syntax. The lines looked like this: x=$(($y/10)) We were indicated at the time that this is because the statement does not use Bourne shell syntax, which is

[Rd] Collaborative Wiki for fostering Open Innovation in R

2017-12-17 Thread Juan Telleria
Dear R Developers, I am writing in order to open a constructive debate whether if it is worth it that R Project adopts the Apache Software Foundation & Wikipedia Model for Open Documentation by using a Collaborative Wiki & Document Store (As a complement to Bugzilla and Mailing Lists), for

[Rd] Issue related to Rlapack

2017-12-17 Thread A Dabral
Hi, I am having an issue regarding R3.4.3. I am launching R instance from RDotNet using following two statements: REngine.SetEnvironmentVariables(rPath, rHome); this._RServer = REngine.GetInstance(); Where rPath = "C:\Program Files\R\R-3.4.3\bin\x64" rHome = "C:\Program Files\R\R-3.4.3" As

Re: [Bioc-devel] workflow page reorganization

2017-12-17 Thread Wolfgang Huber
Thank you all for the efforts on this! I agree with Mike that there's a lot of yet untapped potential in the workflows, for all levels of BioC users: for beginners, to make their first steps, for more experienced users, to learn new stuff. Mike's points 1-5 are great, I second them. And then