Hi,

On Saturday 27 April 2013 11:13:47 meik michalke wrote:
> would a check (for the mere existence of the very expected R binary file) in
> RKWard's startup sequence perhaps be a better place for this? at least it
> would also grant us with an informative error message if the problem occurs
> later, like after an incompatible R upgrade.

hm. Actually, there _is_ such a test in the wrapper script. I wonder why this 
did not trigger... Will have to investigate.

Regards
Thomas

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

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel

Reply via email to