On 09/01/2019 2:16 a.m., Troels Ring wrote:
Dear friends - this is really a question I'm sorry about since it doesn't
follow the requirements. I have made a R package via RStudio and it causes
problems when I try to load some data from within the package. I'm on
windows, R version 3.5.1 (2018-07-
We have a winner! (By bending the rules.)
On 10 January 2019 at 16:44, Kyle Baron wrote:
| Will this work for you?
|
| I had to stash the working directory (when R CMD build is run) in an
| environment variable via ~/.R/build.Renviron`
|
| $ cat ~/.R/build.Renviron
| OLDWD=${PWD}
That is les
On Thu, 10 Jan 2019 at 23:27, Dirk Eddelbuettel wrote:
>
>
> On 10 January 2019 at 22:33, Iñaki Ucar wrote:
> | On Thu, 10 Jan 2019 at 21:55, Dirk Eddelbuettel wrote:
> | > Comes up with an empty / unset olddir when I do
> | >
> | > R CMD build someNameHere; R CMD INSTALL someNameHere_1.2.3.tar
Will this work for you?
I had to stash the working directory (when R CMD build is run) in an
environment variable via ~/.R/build.Renviron`
$ cat ~/.R/build.Renviron
OLDWD=${PWD}
But a Makefile tucked in vignettes directory will run and the two
files will be there in the built package. For me, I
Dear friends - this is really a question I'm sorry about since it doesn't
follow the requirements. I have made a R package via RStudio and it causes
problems when I try to load some data from within the package. I'm on
windows, R version 3.5.1 (2018-07-02).
When I am in the directory with the pac
Dear R package developers
I published a package on CRAN last year (sundialr) which is now failing
with as it is not make to compile a static library with parallel make.
In this package, I compile a static library (libsundials_all.a) from source
files of a third party. The specifics of compiling t
On 10 January 2019 at 22:33, Iñaki Ucar wrote:
| On Thu, 10 Jan 2019 at 21:55, Dirk Eddelbuettel wrote:
| > Comes up with an empty / unset olddir when I do
| >
| > R CMD build someNameHere; R CMD INSTALL someNameHere_1.2.3.tar.gz
|
| This is quite interesting. Because if you run
|
| R CMD bu
On Thu, 10 Jan 2019 at 21:55, Dirk Eddelbuettel wrote:
>
>
> On 9 January 2019 at 17:57, Iñaki Ucar wrote:
> | Did you check Sys.getenv("OLDPWD")? I checked with a knitr vignette
> | and the correct path was there.
>
> Code:
>
> [...]
>
> <>=
> prettyVersion <- packageVersion("someNameHere")
>
On 9 January 2019 at 17:57, Iñaki Ucar wrote:
| Did you check Sys.getenv("OLDPWD")? I checked with a knitr vignette
| and the correct path was there.
Code:
[...]
<>=
prettyVersion <- packageVersion("someNameHere")
prettyDate <- format(Sys.Date(), "%B %e, %Y")
user <- Sys.getenv("USER")
It just ocurred to me the following. Instead of
R CMD build pkg
I've tried this:
cd pkg; R CMD build --log `pwd`
and voilà: the tarball includes a log file, and inside there's the
complete path to the DESCRIPTION.
Iñaki
On Wed, 9 Jan 2019 at 20:33, Duncan Murdoch wrote:
>
> On 09/01/2019 11:
On 09.01.19 20:18, Travers Ching wrote:
> * Use of the AGPL-3 license which seems to be able to cover the ZSTD
> BSD licensce.
ZSTD is dual license BSD and GPL-2. So AGPL-3 is fine, as would be GPL-2
or GPL-3.
> * Attach APGL-3 notice to all my source code files (excluding
> auto-generated Rcpp s
11 matches
Mail list logo
