My thinking is that it works now, why take the risk of messing it up and giving myself the headache? and lastly, (at face value) it’s not possible/easy to switch between versions of R even if you manage to get two or more of them installed.įor these reasons and more, I personally tend to resist updating both R versions and package versions.installing a new (or old) version of R via binary (*.pkg) runs the significant risk of wiping out your current r library.(ideally) a developer should keep in mind that thier users may not have the latest and greatest installation, and may be hesitant to change things on thier local install just to try out a piece of software.some of the new packages I want to leverage within my own project require a more recent R version.many of the packages I had been using are out of date (who has time to keep them updated?).Through this effort I’ve encountered a couple of versioning-related challenges including but not limited to: Please make sure to backup your computer or use TimeMachine prior to giving this a try! Motivation & SetupĪ large portion of my current responsibilities focus on the development and deployment of a new R package. Given all of the varieties of mac OS X, and the innumerable ways of installing and maintaining R I can’t guarantee that the outline below will work for your precise situation.
I’m not a computer scientist nor did I sleep at a Holiday Inn last night.
0 kommentar(er)
