Folks:
What is the policy on adding Windows executables to an R package? My gdalUtils
package could REALLY use this ability (right now it requires users to manually
install GDAL which can cause headaches for folks). Related: what about
linux/mac executables?
Are there reasonable tutorials
Awesome -- the key was the "RD", so for me:
docker run -v /Users:/Users --rm -ti rocker/r-devel RD
(where, on a Mac, I was binding my Mac's /Users to the Docker's /Users
directory)
Thanks, all!
--j
On Wed, Jan 15, 2020 at 2:53 PM Dirk Eddelbuettel
mailto:e...@debian.org>> wrote:
Jonathan,
One of the issues I'm running into is that it seems every time there's a Mac
update something gets broken with regards to compilers, making it incredibly
challenging to get the development install of R working with Rcpp (which is a
requirement for the packages I need to use to check my
Folks:
My package gdalUtils is a wrapper for a set of binaries on disk (the GDAL
Utilities) -- these have about as many places to install as there are people
installing it, and the system environment variables aren't always much help
(they aren't always set) for locating them. My package is
I'm a little confused when documenting my code using Imports vs. Depends.
If I have an example in my .Rd that uses a library that is listed under
Imports, it doesn't work, but if it is listed under Depends, it does. What
is the proper way to go about using examples that rely on an Imports?
Should
Folks:
I am getting a build failure when I:
#' @importFrom utils shortPathName
which roxygenizes it to the NAMESPACE.
I suspect this is because this particular function is Windows-only, but I'm
a bit confused how I should "properly" importFrom a function like this so
it doesn't cause a build
not have any access to.
Another option to system() is pipe()
Paul
On 13-10-30 03:15 PM, Dirk Eddelbuettel wrote:
On 30 October 2013 at 13:54, Jonathan Greenberg wrote:
| R-developers:
|
| I have a small python script that I'd like to include in an R
package I'm
| developing, but I'm
R-developers:
I have a small python script that I'd like to include in an R package I'm
developing, but I'm a bit unclear about which subfolder it should go in. R
will be calling the script via a system() call. Thanks!
--j
--
Jonathan A. Greenberg, PhD
Assistant Professor
Global
I'm working on an update for my CRAN package spatial.tools and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Jonathan Asher Greenberg spatial-to...@estarcion.net'
Depends: includes the non-default packages:
'sp' 'raster'
...@gmail.comwrote:
On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
I'm working on an update for my CRAN package spatial.tools and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Jonathan Asher Greenberg spatial
One more follow-up -- will I now need to include a library() statement in
each function?
--j
On Sun, Oct 20, 2013 at 3:58 PM, Gabor Grothendieck ggrothendi...@gmail.com
wrote:
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
murdoch.dun...@gmail.com wrote:
On 13-10-20 4:43 PM, Jonathan
wrote:
On 20 October 2013 at 16:20, Jonathan Greenberg wrote:
| One more follow-up -- will I now need to include a library() statement in
| each function?
No.
NAMESPACE entry, coupled with Imports: in DESCRIPTION.
Dirk
--
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
R-developers:
Duncan Murdoch suggested I move a post I started on r-help over here,
since it is more at the developer level. Here is my
question/challenge -- to my knowledge, there is not currently an
official way to store a *package*'s options to a standardized location
on a user's computer.
R-developers:
I had a quick question for the group -- let's say a package I am
developing depends on a single, small function from a large
CRAN-listed package. I can, of course, set a dependency within my own
package, but are there means by which I can include the R script + man
file DIRECTLY in
I had a similar question awhile ago. Basically, my understanding is
if it is a function, it needs to be documented UNLESS you are calling
it via :::
--j
On Thu, Aug 29, 2013 at 1:11 PM, Sana Wajid sat3l...@gmail.com wrote:
Thank you all, I appreciate your responses. Just a quick follow up
, Jonathan Greenberg j...@illinois.edu wrote:
I had a similar question awhile ago. Basically, my understanding is
if it is a function, it needs to be documented UNLESS you are calling
it via :::
--j
On Thu, Aug 29, 2013 at 1:11 PM, Sana Wajid sat3l...@gmail.com wrote:
Thank you all, I appreciate
R-developers:
I'm working on updating my R package spatial.tools, and one thing I
was wondering was the proper way to have hidden functions -- should I
simply not export them to the namespace and use the ::: operator to
call them (which is what I currently do)?
--j
--
Jonathan A. Greenberg, PhD
:52 PM, Jonathan Greenberg wrote:
R-developers:
I'm working on updating my R package spatial.tools, and one thing I
was wondering was the proper way to have hidden functions -- should I
simply not export them to the namespace and use the ::: operator to
call them (which is what I currently do
R-developers:
I'm beginning to work on a manuscript for a set of functions I
developed for a package I have on CRAN (spatial.tools), and I'd like
to rename a function in my package to give a better idea of what it
does prior to manuscript submission -- is there a safe way to do a
19 matches
Mail list logo
