Hi,
Thanks for reporting this.
Are you noticing a changed behavior running purely from R, or running R expressions via R.NET? I assume the latter but better ask.
I am not following the recent releases, having being tied to other (lesser...) technologies at work, and cannot intuit what may be going on. .libPaths and underlying stuff should really be pure R behavior so far as I know, so the behavior is intriguing. Even using the R_LIB environment variable should only prepend additional library locations, not override others (see below as I use it to have a version independent library). That said I do not know for sure how it interplays with user's libraries as created by R for non-admin users.
I'll may be able to look at this within a few days if you do not get other help meanwhile.
Thanks for reporting this.
Are you noticing a changed behavior running purely from R, or running R expressions via R.NET? I assume the latter but better ask.
I am not following the recent releases, having being tied to other (lesser...) technologies at work, and cannot intuit what may be going on. .libPaths and underlying stuff should really be pure R behavior so far as I know, so the behavior is intriguing. Even using the R_LIB environment variable should only prepend additional library locations, not override others (see below as I use it to have a version independent library). That said I do not know for sure how it interplays with user's libraries as created by R for non-admin users.
I'll may be able to look at this within a few days if you do not get other help meanwhile.
> .libPaths()
[1] "f:/Rlib" "C:/Program Files/R/R-3.0.1/library"