I've written a fairly elaborate package (called "eoa") that relies
on
functions from several other packages. I've built the package into a zip
file on Windows using Hadley's devtools::build(binary = T) and have sent
the zip to a couple dozen people for testing. My package installs fine, but
some people are having trouble loading it. After library(eoa), they get
something like:
Error: could not load package tcltk2
In DESCRIPTION file, I use
Depends: tcltk, tcltk2, tkrplot
Imports: actuar,
graphics,
gsl,
MASS,
Matrix,
tensorA
If, after getting the "could not load" message, the user installs the
required packages by hand, everything works fine.
My understanding was that both the "Depends: " and the "Imports:
" lines in
DESCRIPTION file direct R to automatically install required packages that
haven't been previously installed.
It doesn't appear to be working that way for me. There must be a simple
solution that I am obviously missing....
Any help would be greatly appreciated!
-Dan
--
Dan Dalthorp, PhD
USGS Forest and Rangeland Ecosystem Science Center
Forest Sciences Lab, Rm 189
3200 SW Jefferson Way
Corvallis, OR 97331
ph: 541-750-0953
ddalthorp at usgs.gov
[[alternative HTML version deleted]]
>>>>> Dalthorp, Daniel <ddalthorp at usgs.gov> >>>>> on Thu, 28 Apr 2016 16:41:28 -0700 writes:> I've written a fairly elaborate package (called "eoa") > that relies on functions from several other packages. I've > built the package into a zip file on Windows using > Hadley's devtools::build(binary = T) and have sent the zip > to a couple dozen people for testing. My package installs > fine, but some people are having trouble loading it. After > library(eoa), they get something like: > Error: could not load package tcltk2 > In DESCRIPTION file, I use > Depends: tcltk, tcltk2, tkrplot > Imports: actuar, graphics, gsl, MASS, Matrix, tensorA > If, after getting the "could not load" message, the user > installs the required packages by hand, everything works > fine. > My understanding was that both the "Depends: " and the > "Imports: " lines in DESCRIPTION file direct R to > automatically install required packages that haven't been > previously installed. All package installation happens via install.packages(), at least eventually. If you look at the help page for that, it has always said that it does not (as it cannot easily, in general!!) look at dependencies when you do not install from a repository. This question would clearly have belonged to R-help, not R-devel. I'm CC ing to the help list and am asking all follow-ups to go *only* to R-help, please. Martin > It doesn't appear to be working that way for me. There > must be a simple solution that I am obviously missing.... > Any help would be greatly appreciated! > -Dan > -- > Dan Dalthorp, PhD USGS Forest and Rangeland Ecosystem > Science Center Forest Sciences Lab, Rm 189 3200 SW > Jefferson Way Corvallis, OR 97331 ph: 541-750-0953 > ddalthorp at usgs.gov
On 28 April 2016 at 16:41, Dalthorp, Daniel wrote: | I've written a fairly elaborate package (called "eoa") that relies on | functions from several other packages. I've built the package into a zip | file on Windows using Hadley's devtools::build(binary = T) and have sent | the zip to a couple dozen people for testing. My package installs fine, but | some people are having trouble loading it. After library(eoa), they get | something like: | | Error: could not load package tcltk2 | | In DESCRIPTION file, I use | | Depends: tcltk, tcltk2, tkrplot | Imports: actuar, | graphics, | gsl, | MASS, | Matrix, | tensorA | | If, after getting the "could not load" message, the user installs the | required packages by hand, everything works fine. | | My understanding was that both the "Depends: " and the "Imports: " lines in | DESCRIPTION file direct R to automatically install required packages that | haven't been previously installed. | | It doesn't appear to be working that way for me. There must be a simple | solution that I am obviously missing.... I think this would work if you users installed from a _repository_ rather than a single zip file. So in a sense I feat it is a flaw in the setup you provided. You can build repositories, both local / private and visible / public, using the drat package: http://dirk.eddelbuettel.com/code/drat.html, also on CRAN. Else, just have them execute a helper script you devise.... Dirk | Any help would be greatly appreciated! | | -Dan | | -- | Dan Dalthorp, PhD | USGS Forest and Rangeland Ecosystem Science Center | Forest Sciences Lab, Rm 189 | 3200 SW Jefferson Way | Corvallis, OR 97331 | ph: 541-750-0953 | ddalthorp at usgs.gov | | [[alternative HTML version deleted]] | | ______________________________________________ | R-devel at r-project.org mailing list | https://stat.ethz.ch/mailman/listinfo/r-devel -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org