Skip to content
Back to formatted view

Raw Message

Message-ID: <CABghstRtyCw3G4zpyu1Uu=tn3po8-uv0zX=G+ozhZEF5uRn_GA@mail.gmail.com>
Date: 2020-01-22T21:07:04Z
From: Ben Bolker
Subject: [R-pkg-devel] Adding .exes to R package?
In-Reply-To: <CABghstTdkEO9mjjsm3bxdFxqohX4YbN_2smQURR-wBKeP2W3tA@mail.gmail.com>

PS I don't know if you would be allowed to include a utility function
to be run manually by users after setup that would download binaries
from a trusted source and put them in an appropriate/findable place on
the user's system.

On Wed, Jan 22, 2020 at 4:06 PM Ben Bolker <bbolker at gmail.com> wrote:
>
> From https://cran.r-project.org/web/packages/policies.html:
>
> Source packages may not contain any form of binary executable code.
>
>
>
> On Wed, Jan 22, 2020 at 3:54 PM Jonathan Greenberg <jgreenberg at unr.edu> wrote:
> >
> > 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 on how to do this?
> >
> > --j
> >
> >         [[alternative HTML version deleted]]
> >
> > ______________________________________________
> > R-package-devel at r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel