[Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
Hi, Who should I ask about my package Rigroup_0.83 being moved to Archive status on CRAN and no longer available via install.package? I have no problems with the move if this was simply because of low demand. However, if there was a build issue with the newest releases that caused problems, I

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
4:00 PM, Henrik Bengtsson wrote: > On Sat, Mar 9, 2013 at 12:25 PM, Kevin Hendricks > wrote: >> Hi, >> >> Who should I ask about my package Rigroup_0.83 being moved to Archive status >> on CRAN and no longer available via install.package? I have no problems

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
. Thanks, Kevin Sent from my iPad On 2013-03-09, at 4:38 PM, Kevin Hendricks wrote: > Hi, > Thanks for that info. It works/builds without error or warnings on my RedHat > Enterprise 6 with R 2.15.2 version which I use but must be broken somehow on > later versions. I will

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
Hi Dan, Thank you! I dig up a Mac at work and recreate this. Kevin On 2013-03-09, at 5:52 PM, Dan Tenenbaum wrote: > On Sat, Mar 9, 2013 at 2:17 PM, Kevin Hendricks > wrote: >> Hi, >> One last quick question ... does anyone archive older CRAN package check >> summar

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
Hi Dan, In case this catches anyone else ... FWIW, I found the issue ... in my Rinit.c, my package uses the .External call which actually takes one SEXP which points to a "varargs-like" list. Under 2.15.X and earlier, I thought the proper entry for an .External call was as below since it onl

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-10 Thread Kevin Hendricks
ou never answered nor fixed the package, hence the > package has been archived. > > Best, > Uwe Ligges > > > > > On 10.03.2013 02:43, Kevin Hendricks wrote: >> Hi Dan, >> >> In case this catches anyone else ... >> >> FWIW, I found the issue

[Rd] Withdrawal of package Rigroup-0.84.0 from CRAN

2013-04-20 Thread Kevin Hendricks
Hi Brian and Uwe, Given my package passes all checks but I have received no further responses since your initial reply, I assume you are no longer interested in the package Rigroup-0.84.0. Your concerns about my chosen license being too vague "GPL | LGPL" is in direct contradiction to what you

Re: [Rd] New package test results available

2009-02-07 Thread Kevin Hendricks
Hi, I am the maintainer for the Rigroup package. Based on the e-mail below, I found and fixed a warning (spurious right brace) in the manual for my package under the new parser. It has been a number of years since I last revised the package and I am not sure where and how to upload it.

Re: [Rd] New package test results available

2009-02-07 Thread Kevin Hendricks
-Feb-09, at 11:39 AM, Kevin Hendricks wrote: Hi, I am the maintainer for the Rigroup package. Based on the e-mail below, I found and fixed a warning (spurious right brace) in the manual for my package under the new parser. It has been a number of years since I last revised the package and I

Re: [Rd] R thread safe

2009-03-18 Thread Kevin Hendricks
Hi, I don't think so, because IMHO it makes no sense - you're missing the main point that R is not thread safe. There are ways to use threads from within R very cautiously (see Luke's parallelized vector math operations for R for example). There are many good methods to use threads in