Re: [R-pkg-devel] implications of staged install for data processing packages

2019-06-28 Thread Florian Oswald
brilliant! thanks a lot, and yes, will come back with more in case I'm stuck. F On Fri, 28 Jun 2019 at 17:44, Tomas Kalibera wrote: > On 6/28/19 5:16 PM, Florian Oswald wrote: > > oh ok i see: so i will always be able to do > > > > clean(path = "~/data.csv") > > > > for example? in that case I

Re: [R-pkg-devel] implications of staged install for data processing packages

2019-06-28 Thread Tomas Kalibera
On 6/28/19 5:16 PM, Florian Oswald wrote: oh ok i see: so i will always be able to do clean(path = "~/data.csv") for example? in that case I completely misunderstood this and there must indeed be some system.file call buried somewhere. will check. thanks! In case it is hard to find manually,

Re: [R-pkg-devel] implications of staged install for data processing packages

2019-06-28 Thread Florian Oswald
oh ok i see: so i will always be able to do clean(path = "~/data.csv") for example? in that case I completely misunderstood this and there must indeed be some system.file call buried somewhere. will check. thanks! Florian On Fri, 28 Jun 2019 at 17:11, Georgi Boshnakov < georgi.boshna...@manches

Re: [R-pkg-devel] implications of staged install for data processing packages

2019-06-28 Thread Georgi Boshnakov
You need to give details what exactly gets you into trouble and about your use case, since any advice would be conditional on making assumptions about that. It is usually a bad a idea to have a function working on a hardcoded full filename. You will thank yourself later if you at least make it a

[R-pkg-devel] implications of staged install for data processing packages

2019-06-28 Thread Florian Oswald
Hi all I ran into trouble with the changes starting to come in with R3.6 stemming from the new staged installation, which checks and errors on hard coded paths in R code. I understand there is an opt out, but still want to know. here's the blog post: https://developer.r-project.org/Blog/public/201

Re: [R-pkg-devel] Warning: replacing previous import ...

2019-06-28 Thread Ralf Stubner
Hi Christian, in your NAMESPACE you import both mvtnorm and mclust completely. The warning should go away if you change this to importFrom(...) with only the methods you actually need, in particular dmvnorm either from mvtnorm or from mclust. Alternatively, you could leave out the imports and alwa

[R-pkg-devel] Warning: replacing previous import ...

2019-06-28 Thread Christian Martin Hennig
Dear list, I'm maintainer of the fpc package and got an email that I need to replace a warning that has come up. The warning is: "Warning: replacing previous import ‘mclust::dmvnorm’ by ‘mvtnorm::dmvnorm’ when loading ‘fpc’" Back story: A few month ago I was contacted by the maintainer of mclu