You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not sure if you are creating this symlink, but the downloadable Rserve_1.8-1.tar.gz tarball from CRAN contains a symlink
clients -> src/client
which messed up my attempts to get it to install under R-3.1.1 on linux as a Recommended package during initial R build-from-source. The untar2 built-in function gets confused by the symlink and leaves us in the wrong /tmp directory after untaring, instead of the original Recommended directory, and the R build crashes. Arg.
Anyway, I realize this is more of a packagers bug, but if you have any influence, could you direct this note to who does the packaging? Thank you. I know not everyone wants Rserve as a recommended package (fools!) but I do. :)
Jason
The text was updated successfully, but these errors were encountered:
This seems more like a bug in R :) The packaging is done by mkdist which creates that symlink. I'm not sure why that symlink specifically should confuse R, though. It's just a convenience symlink, really.
Hi Simon,
not sure if you are creating this symlink, but the downloadable Rserve_1.8-1.tar.gz tarball from CRAN contains a symlink
clients -> src/client
which messed up my attempts to get it to install under R-3.1.1 on linux as a Recommended package during initial R build-from-source. The untar2 built-in function gets confused by the symlink and leaves us in the wrong /tmp directory after untaring, instead of the original Recommended directory, and the R build crashes. Arg.
Anyway, I realize this is more of a packagers bug, but if you have any influence, could you direct this note to who does the packaging? Thank you. I know not everyone wants Rserve as a recommended package (fools!) but I do. :)
Jason
The text was updated successfully, but these errors were encountered: