Am Mittwoch, 12. November 2014, 14:07:17 schrieb Thomas Friedrichsmeier:
> Well, the one thing going for CRAN is that we're including it as a repo, 
> anyway.

true, but the overhead of *publishing* all our packages there would be 
enormous. right now we can package and publish everything ourselves. if we 
were using CRAN, every single package would need to go through the CRAN 
review, and they usually find some little detail they don't like (half of the 
time it has nothing to do with the actual package quality, more like "we don't 
want it, don't do it"). then you need to repackage and resubmit, again wait 
for the review, and they'll find something else (like a README file they don't 
understand, so they want you to remove it)... sometimes that's great quality 
control for actual R packages, but we don't even ship R code. i can imagine 
what the reply would be to our initial submission ;-)

i think it would be impossible to have a package like rkwarddev on CRAN, 
because it uses functions from the rkward package, which in turn is not on 
CRAN (hence their buildbots would fail). i highly doubt that the CRAN 
maintainers would allow rkward to be published there, nor what it would imply 
for users running older versions of RKWard if they upgrade to the newest 
rkward package.

viele grüße :: m.eik

  dipl. psych. meik michalke
  institut f"ur experimentelle psychologie
  abt. f"ur diagnostik und differentielle psychologie
  heinrich-heine-universit"at d-40204 d"usseldorf

Attachment: signature.asc
Description: This is a digitally signed message part.

Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
RKWard-devel mailing list

Reply via email to