Cran R Download Mac
2020年11月15日Download: http://gg.gg/n1r0t
So you can just type in CRAN here. And you’ll see that there are a number of options for you to download here for different platforms. We’re going to download the Mac platform here, so we can go to Download R for the Mac and you see that the latest version here is version 3.0.3. Select a CRAN location (a mirror site) and click the corresponding link. Click on the ’Download R for (Mac) OS X’ link at the top of the page. Click on the file containing the latest version of R under ’Files.’ Save the.pkg file, double-click it to open, and follow the installation instructions.
The aim of devtools is to make your life as a package developer easier by providing R functions that simplify many common tasks. R packages are actually really simple, and with the right tools it should be easier to use the package structure than not. Package development in R can feel intimidating, but devtools does every thing it can to make it as welcoming as possible. devtools comes with a small guarantee: if because of a bug in devtools a member of R-core gets angry with you, I will send you a handwritten apology note. Just forward me the email and your address, and I’ll get a card in the mail.
devtools is opinionated about how to do package development, and requires that you use roxygen2 for documentation and testthat for testing. Not everyone agrees with these opinions, and they are by no means perfect, but they have evolved during the process of writing over 30 R packages. I’m always happy to hear about what doesn’t work for you, and any places where devtools gets in your way. Either send an email to the rdevtools mailing list or file an issue.Updating to the latest version of devtools
You can track (and contribute to) development of devtools at https://github.com/hadley/devtools. To install it:
*
Install the release version of devtools from CRAN with install.packages(’devtools’).
*Make sure you have a working development environment.
*Windows: Install Rtools.
*Mac: Install Xcode from the Mac App Store.
*Linux: Install a compiler and various development libraries (details vary across differnet flavors of Linux).
*
Follow the instructions below depending on platform.
*
Mac and Linux:
*
Windows:Package development tools
All devtools functions accept a path as an argument, e.g. load_all(’path/to/path/mypkg’). If you don’t specify a path, devtools will look in the current working directory - this is recommend practice.
Frequent development tasks:
*
load_all() simulates installing and reloading your package, loading R code in R/, compiled shared objects in src/ and data files in data/. During development you usually want to access all functions so load_all() ignores the package NAMESPACE. load_all() will automatically create a DESCRIPTION if needed.
*
document() updates documentation, file collation and NAMESPACE.
*
test() reloads your code, then runs all testthat tests.
Building and installing:
*
install() reinstalls the package, detaches the currently loaded version then reloads the new version with library(). Reloading a package is not guaranteed to work: see the documentation to unload() for caveats.
*
build() builds a package file from package sources. You can can use it to build a binary version of your package.
*
install_github() installs an R package from github, install_gitorious() from gitorious, install_bitbucket() from bitbucket, install_url() from an arbitrary url and install_file() from a local file on disk. install_version() installs a specified version from cran.
Check and release:
*
check() updates the documentation, then builds and checks the package. build_win() builds a package using win-builder, allowing you to easily check your package on windows.
*
run_examples() will run all examples to make sure they work. This is useful because example checking is the last step of R CMD check.
*
check_doc() runs most of the documentation checking components of R CMD check
*
release() makes sure everything is ok with your package (including asking you a number of questions), then builds and uploads to CRAN. It also drafts an email to let the CRAN maintainers know that you’ve uploaded a new package.
Other commands:
*
bash() opens a bash shell in your package directory so you can use git or other command line tools.
*
wd() changes the working directory to a path relative to the package root.Development mode
Calling dev_mode() will switch your version of R into ’development mode’. In this mode, R will install packages to ~/R-dev. This is useful to avoid clobbering the existing versions of CRAN packages that you need for other tasks. Calling dev_mode() again will turn development mode off, and return you to your default library setup.Other tips
I recommend adding the following code to your .Rprofile:
See the complete list in ?devtools
This will set up R to:
*always install packages from the RStudio CRAN mirror
*ignore newlines when browse()ing
*give minimal output from traceback()
*automatically load devtools in interactive sessions
There are also a number of options you might want to set (in .Rprofile) to customise the default behaviour when creating packages and drafting emails:
*devtools.name: your name, used to sign emails
*devtools.desc.author: your R author string, in the form of ’Hadley Wickham <h.wickham@gmail.com> [aut, cre]’. Used when creating default DESCRIPTION files.
*devtools.desc.license: a default license used when creating new packagesThis is the new home for experimental binaries and documentation related to R for macOS. To learn more about the R software or download released versions, please visit www.r-project.org.Download R Packages From Cran
All software on this page is strictly experimental and subject to acceptance of the supplied R license agreement and the disclaimer at the end of the page.Important note about R 4.0.0Starting with R 4.0.0 alpha we are building R using standard Apple tools (Xcode 11.4) and GNU Fortran 8.2 from fxcoudert and the target is macOS 10.13 (High Sierra). All dependent static libraries are available in the libs-4 directory. Please make sure you remove any modifications to build flags from your home since no custom compilers are used anymore. For more information about alternative OpenMP options (as in older version) see the openmp page of this site.IndexNightly builds for macOSR frameworkBuildOSDateStatusDownloadR-3.6-branch3.6.3 Patched(2020/04/28, r79401)el-capitanNov 5 23:30x86_64: OK (log)Package: OKR-3.6-branch-el-capitan-sa-x86_64.tar.gz (67Mb)R-3.6-branch-el-capitan-signed.pkg (77Mb, installer incl. GUI)R-4.0-branch4.0.3 Patched(2020/11/02, r79401)high-sierraNov 5 21:41x86_64: OK (log)Package: OKR-4.0-branch.tar.gz (73Mb)R-4.0-branch.pkg (85Mb, installer incl. GUI)R-devel4.1.0 Under development (unstable)(2020/11/05, r79401)high-sierraNov 5 21:52x86_64: OK (log)Package: OKR-devel.tar.gz (73Mb)R-devel.pkg (85Mb, installer incl. GUI)
The installer image (*.pkg) is packaged exactly the same way as the CRAN release of R (including the GUI) and it will update your R version (unless you use pkgutil - see instructions during installation and/or the ’Multiple versions’section of the R Installation and Administration manual).
Alternatively, you can use the tar-ball (*.tar.gz) in the table above. The tar-ball must be unpacked in the root directory using:$ tar fvxz R*.tar.gz -C /
NOTE: The tar-ball does not contain the GUI (see below for a separate download).
NOTE: The installer includes Tcl/Tk package which will install in /usr/local. It is optional (only needed for the tcltk R package) and can be unchecked at installation time.
If you see any issues with the builds, please contact Simon Urbanek (the macOS maintainer of R) or report on the R-SIG-Mac mailing list.Mac OS X GUIVersionBuildDownloadMac OS X GUI rev. 7782 for R 3.6.xel-capitan-Debug.dmgR-GUI-7782-3.6-el-capitan-Debug.dmgMac OS X GUI rev. 7782 for R 3.6.xel-capitan-Release.dmgR-GUI-7782-3.6-el-capitan-Release.dmgMac OS X GUI rev. 7898 for R 4.0.xhigh-sierra-Debug.dmgR-GUI-7898-4.0-high-sierra-Debug.dmgMac OS X GUI rev. 7898 for R 4.0.xhigh-sierra-Release.dmgR-GUI-7898-4.0-high-sierra-Release.dmgMac OS X GUI rev. 7898 for R 4.1.xhigh-sierra-Debug.dmgR-GUI-7898-4.1-high-sierra-Debug.dmgMac OS X GUI rev. 7898 for R 4.1.xhigh-sierra-Release.dmgR-GUI-7898-4.1-high-sierra-Release.dmg
To install, open the image and drag the R icon to your Applications folder. Alternatively the GUI can be run directly off that image without copying if you just want to test it. Build configurations with ’64’ suffix are 64-bit builds, all others are 32-bit (except for Debug). If you want to use both, rename one of them or place them in different directories.ToolsIn order to compile R and R packages you will need Xcode Developer ToolsCran R Download For Mac and a Fortran compiler. For details and download, please read the Tools page. The R 4.0.0 and higer binaries are built using Xcode 11.4.Experimental binary packagesThis site no longer hosts experimental packages. It is now the master repository for released R package binaries. If you have issues with other mirrors, try using https://mac.r-project.org/ as your mirror as it is updated first.Legacy RCran.r-project.org Download MacThe current build supports only macOS X 10.13 (High Sierra) or higher. Older versions of macOS are not supported in binary form, but R can be compiled from sources for such legacy OS versions. Last released version for Mac OS X 10.4 (Tiger) was R 2.10.1, last release for Mac OS X 10.5 (Leopard) was R 2.15.3, last release for Mac OS X 10.11 (El Capitan) was R 3.6.3.Other binariesThe following binaries are not maintained or supported by R-core and are provided without any guarantee and for convenience only (Mac OS X 10.4.4 or higher required). They match the binaries used on the CRAN binary build machine and thus are recommended for use with CRAN R package binaries.
*GTK+ 2.24.17 framework - 64-bit build of GTK+ 2.24.17, necessary for binary R packages that use GTK+ version 2 (such as RGtk2+). R 3.0.0 and higher, Snow Leopard buildDownload: GTK_2.24.17-X11.pkg (ca. 41MB)
*GTK+ 2.18.5 framework - universal build of GTK+ 2.18.5, necessary for binary R packages that use GTK+ version 2 (such as RGtk2+). R 2.10.0 - 2.15.3, Leopard buildDownload: GTK_2.18.5-X11.pkg (ca. 58MB)
*RSwitch - a small GUI that allows you to switch between R versions quickly (if you have multiple versions of R framework installed).Download: RSwitch-1.2.dmg (ca 67kB, universal, updated 2011/03/24 to support R 2.13.0 and up)Sources: RSwitch-1.2.tar.gz (Xcode project and sources)
NOTE: Bob Rudis is maintaining a new version of a tool which has RSwitch functionality and more - see 3rd party RSwitch replacement (NOT related to R-Foundation or CRAN!).Cran Project
More external libraries for R 4.0.0 and higher can be found in the /libs-4/ directory. For older versions see the /libs/ directory.DisclaimerAll software is provided ’as is’ and any express or implied warranties, including, but but not limited to the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the publisher, copyright owner or contributors be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
Download: http://gg.gg/n1r0t
So you can just type in CRAN here. And you’ll see that there are a number of options for you to download here for different platforms. We’re going to download the Mac platform here, so we can go to Download R for the Mac and you see that the latest version here is version 3.0.3. Select a CRAN location (a mirror site) and click the corresponding link. Click on the ’Download R for (Mac) OS X’ link at the top of the page. Click on the file containing the latest version of R under ’Files.’ Save the.pkg file, double-click it to open, and follow the installation instructions.
The aim of devtools is to make your life as a package developer easier by providing R functions that simplify many common tasks. R packages are actually really simple, and with the right tools it should be easier to use the package structure than not. Package development in R can feel intimidating, but devtools does every thing it can to make it as welcoming as possible. devtools comes with a small guarantee: if because of a bug in devtools a member of R-core gets angry with you, I will send you a handwritten apology note. Just forward me the email and your address, and I’ll get a card in the mail.
devtools is opinionated about how to do package development, and requires that you use roxygen2 for documentation and testthat for testing. Not everyone agrees with these opinions, and they are by no means perfect, but they have evolved during the process of writing over 30 R packages. I’m always happy to hear about what doesn’t work for you, and any places where devtools gets in your way. Either send an email to the rdevtools mailing list or file an issue.Updating to the latest version of devtools
You can track (and contribute to) development of devtools at https://github.com/hadley/devtools. To install it:
*
Install the release version of devtools from CRAN with install.packages(’devtools’).
*Make sure you have a working development environment.
*Windows: Install Rtools.
*Mac: Install Xcode from the Mac App Store.
*Linux: Install a compiler and various development libraries (details vary across differnet flavors of Linux).
*
Follow the instructions below depending on platform.
*
Mac and Linux:
*
Windows:Package development tools
All devtools functions accept a path as an argument, e.g. load_all(’path/to/path/mypkg’). If you don’t specify a path, devtools will look in the current working directory - this is recommend practice.
Frequent development tasks:
*
load_all() simulates installing and reloading your package, loading R code in R/, compiled shared objects in src/ and data files in data/. During development you usually want to access all functions so load_all() ignores the package NAMESPACE. load_all() will automatically create a DESCRIPTION if needed.
*
document() updates documentation, file collation and NAMESPACE.
*
test() reloads your code, then runs all testthat tests.
Building and installing:
*
install() reinstalls the package, detaches the currently loaded version then reloads the new version with library(). Reloading a package is not guaranteed to work: see the documentation to unload() for caveats.
*
build() builds a package file from package sources. You can can use it to build a binary version of your package.
*
install_github() installs an R package from github, install_gitorious() from gitorious, install_bitbucket() from bitbucket, install_url() from an arbitrary url and install_file() from a local file on disk. install_version() installs a specified version from cran.
Check and release:
*
check() updates the documentation, then builds and checks the package. build_win() builds a package using win-builder, allowing you to easily check your package on windows.
*
run_examples() will run all examples to make sure they work. This is useful because example checking is the last step of R CMD check.
*
check_doc() runs most of the documentation checking components of R CMD check
*
release() makes sure everything is ok with your package (including asking you a number of questions), then builds and uploads to CRAN. It also drafts an email to let the CRAN maintainers know that you’ve uploaded a new package.
Other commands:
*
bash() opens a bash shell in your package directory so you can use git or other command line tools.
*
wd() changes the working directory to a path relative to the package root.Development mode
Calling dev_mode() will switch your version of R into ’development mode’. In this mode, R will install packages to ~/R-dev. This is useful to avoid clobbering the existing versions of CRAN packages that you need for other tasks. Calling dev_mode() again will turn development mode off, and return you to your default library setup.Other tips
I recommend adding the following code to your .Rprofile:
See the complete list in ?devtools
This will set up R to:
*always install packages from the RStudio CRAN mirror
*ignore newlines when browse()ing
*give minimal output from traceback()
*automatically load devtools in interactive sessions
There are also a number of options you might want to set (in .Rprofile) to customise the default behaviour when creating packages and drafting emails:
*devtools.name: your name, used to sign emails
*devtools.desc.author: your R author string, in the form of ’Hadley Wickham <h.wickham@gmail.com> [aut, cre]’. Used when creating default DESCRIPTION files.
*devtools.desc.license: a default license used when creating new packagesThis is the new home for experimental binaries and documentation related to R for macOS. To learn more about the R software or download released versions, please visit www.r-project.org.Download R Packages From Cran
All software on this page is strictly experimental and subject to acceptance of the supplied R license agreement and the disclaimer at the end of the page.Important note about R 4.0.0Starting with R 4.0.0 alpha we are building R using standard Apple tools (Xcode 11.4) and GNU Fortran 8.2 from fxcoudert and the target is macOS 10.13 (High Sierra). All dependent static libraries are available in the libs-4 directory. Please make sure you remove any modifications to build flags from your home since no custom compilers are used anymore. For more information about alternative OpenMP options (as in older version) see the openmp page of this site.IndexNightly builds for macOSR frameworkBuildOSDateStatusDownloadR-3.6-branch3.6.3 Patched(2020/04/28, r79401)el-capitanNov 5 23:30x86_64: OK (log)Package: OKR-3.6-branch-el-capitan-sa-x86_64.tar.gz (67Mb)R-3.6-branch-el-capitan-signed.pkg (77Mb, installer incl. GUI)R-4.0-branch4.0.3 Patched(2020/11/02, r79401)high-sierraNov 5 21:41x86_64: OK (log)Package: OKR-4.0-branch.tar.gz (73Mb)R-4.0-branch.pkg (85Mb, installer incl. GUI)R-devel4.1.0 Under development (unstable)(2020/11/05, r79401)high-sierraNov 5 21:52x86_64: OK (log)Package: OKR-devel.tar.gz (73Mb)R-devel.pkg (85Mb, installer incl. GUI)
The installer image (*.pkg) is packaged exactly the same way as the CRAN release of R (including the GUI) and it will update your R version (unless you use pkgutil - see instructions during installation and/or the ’Multiple versions’section of the R Installation and Administration manual).
Alternatively, you can use the tar-ball (*.tar.gz) in the table above. The tar-ball must be unpacked in the root directory using:$ tar fvxz R*.tar.gz -C /
NOTE: The tar-ball does not contain the GUI (see below for a separate download).
NOTE: The installer includes Tcl/Tk package which will install in /usr/local. It is optional (only needed for the tcltk R package) and can be unchecked at installation time.
If you see any issues with the builds, please contact Simon Urbanek (the macOS maintainer of R) or report on the R-SIG-Mac mailing list.Mac OS X GUIVersionBuildDownloadMac OS X GUI rev. 7782 for R 3.6.xel-capitan-Debug.dmgR-GUI-7782-3.6-el-capitan-Debug.dmgMac OS X GUI rev. 7782 for R 3.6.xel-capitan-Release.dmgR-GUI-7782-3.6-el-capitan-Release.dmgMac OS X GUI rev. 7898 for R 4.0.xhigh-sierra-Debug.dmgR-GUI-7898-4.0-high-sierra-Debug.dmgMac OS X GUI rev. 7898 for R 4.0.xhigh-sierra-Release.dmgR-GUI-7898-4.0-high-sierra-Release.dmgMac OS X GUI rev. 7898 for R 4.1.xhigh-sierra-Debug.dmgR-GUI-7898-4.1-high-sierra-Debug.dmgMac OS X GUI rev. 7898 for R 4.1.xhigh-sierra-Release.dmgR-GUI-7898-4.1-high-sierra-Release.dmg
To install, open the image and drag the R icon to your Applications folder. Alternatively the GUI can be run directly off that image without copying if you just want to test it. Build configurations with ’64’ suffix are 64-bit builds, all others are 32-bit (except for Debug). If you want to use both, rename one of them or place them in different directories.ToolsIn order to compile R and R packages you will need Xcode Developer ToolsCran R Download For Mac and a Fortran compiler. For details and download, please read the Tools page. The R 4.0.0 and higer binaries are built using Xcode 11.4.Experimental binary packagesThis site no longer hosts experimental packages. It is now the master repository for released R package binaries. If you have issues with other mirrors, try using https://mac.r-project.org/ as your mirror as it is updated first.Legacy RCran.r-project.org Download MacThe current build supports only macOS X 10.13 (High Sierra) or higher. Older versions of macOS are not supported in binary form, but R can be compiled from sources for such legacy OS versions. Last released version for Mac OS X 10.4 (Tiger) was R 2.10.1, last release for Mac OS X 10.5 (Leopard) was R 2.15.3, last release for Mac OS X 10.11 (El Capitan) was R 3.6.3.Other binariesThe following binaries are not maintained or supported by R-core and are provided without any guarantee and for convenience only (Mac OS X 10.4.4 or higher required). They match the binaries used on the CRAN binary build machine and thus are recommended for use with CRAN R package binaries.
*GTK+ 2.24.17 framework - 64-bit build of GTK+ 2.24.17, necessary for binary R packages that use GTK+ version 2 (such as RGtk2+). R 3.0.0 and higher, Snow Leopard buildDownload: GTK_2.24.17-X11.pkg (ca. 41MB)
*GTK+ 2.18.5 framework - universal build of GTK+ 2.18.5, necessary for binary R packages that use GTK+ version 2 (such as RGtk2+). R 2.10.0 - 2.15.3, Leopard buildDownload: GTK_2.18.5-X11.pkg (ca. 58MB)
*RSwitch - a small GUI that allows you to switch between R versions quickly (if you have multiple versions of R framework installed).Download: RSwitch-1.2.dmg (ca 67kB, universal, updated 2011/03/24 to support R 2.13.0 and up)Sources: RSwitch-1.2.tar.gz (Xcode project and sources)
NOTE: Bob Rudis is maintaining a new version of a tool which has RSwitch functionality and more - see 3rd party RSwitch replacement (NOT related to R-Foundation or CRAN!).Cran Project
More external libraries for R 4.0.0 and higher can be found in the /libs-4/ directory. For older versions see the /libs/ directory.DisclaimerAll software is provided ’as is’ and any express or implied warranties, including, but but not limited to the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the publisher, copyright owner or contributors be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
Download: http://gg.gg/n1r0t
コメント