问题
I'm writing an R package that has several dependencies of other packages, some of them are available in CRAN and other ones are homemade.
According to the help, library("my_package")
will load the namespace of the package once I have previously installed it, i.e, install.package("my_package")
.
Nevertheless, once I have installed the package I am able to use all the functions of the installed but not loaded package through my_package::my_function()
, so if my package has dependencies, beside adding those into DESCRIPTION
file:
Imports:
dplyr,
my_package2,
ggvis,
in the root of the package folder.
Do I have to load the dependencies of the new package through library()
or the final user will see an error if he has not installed on his computer as the required packages are specified in the Imports section?
回答1:
No, the user does not have to load the packages that are used by functions in my_package
.
The fact that you have listed a package under Imports:
in the DESCRIPTION
file means that during the installation of my_package
, R will check that this package is available on your system. This means then that functions in my_package
can use functions from these packages using the ::
notation, as you suggested.
Using the ::
notation is the recommended way to refer to functions from other packages, but there are also other options:
In order to make all the functions from, say,
dplyr
accessable without::
inmy_package
, you could addimport(dplyr)
to theNAMESPACE
file. This is convenient, if you use many functions from a package.If you intend to use only, say, the function
select
fromdplyr
, you could addimportFrom(select, dplyr)
to theNAMESPACE
file.You could also add the package to the
DESCRIPTION
file underDepends:
. This would mean that the package is loaded to the global environment when you uselibrary(my_package)
. This is almost never a good solution.
The general idea of dependencies is R is that my_package
will have "it's own version" of the packages it depends on loaded. Therefore, you can always be sure that you will, e.g., use the function select()
from the dplyr
package, as you intended to do. The exception is the use of Depends:
which bypasses this system. In this case, my_package
will look for functions in the global environment and if somebody should have defined some function called select()
in the global environment, my_package
will use this function and you will get unexpected results.
Example 1:
DESCRIPTION
file:
Imports:
dpylr
some function from my_package
:
my_fun <- function(...) {
dplyr::mutate(...) %>%
dplyr::select(1:3)
}
Example 2:
DESCRIPTION
file:
Imports:
dpylr
NAMESPACE
file:
import(dplyr)
some function from my_package
:
my_fun <- function(...) {
mutate(...) %>%
select(1:3)
}
Example 3:
DESCRIPTION
file:
Imports:
dpylr
NAMESPACE
file:
importFrom(dplyr,select)
some function from my_package
:
my_fun <- function(...) {
dpylr::mutate(...) %>%
select(1:3)
}
You find more detailed explanations of how to handle dependencies in R packages on the web. For instance the following are useful:
- On the DESCRIPTION file
- On the NAMESPACE file
Also, it is not necessary to write the NAMESPACE
file by hand. You can let roxygen2
do that for you. Read the documentation for more information.
来源:https://stackoverflow.com/questions/34880161/use-dependencies-in-r-packages-through-library-description-file