[R-pkg-devel] Solution to function name duplication problem

2020-02-09 Thread sierrastew
Last week I asked for help with a function name duplication problem. I had renamed the project and renamed the functions in the project. Example: needed mvn() from the package MVN, but mvn() is also in thle package mgcv, from which I needed a different function. Using importFrom, or including th

Re: [R-pkg-devel] function name conflict problem

2020-02-05 Thread sierrastew
Thanks to all who responded. Correct that package ‘karon’ is the problem. The current package has a more meaningful name. ‘karon’ was the earlier name; functions have been renamed. I deleted all the old function files, though they had been Committed to GitHub. A colleague working with me wro

Re: [R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
Thanks. I had seen this but it didn't register. I made this change to all the potential conflicts (the packages ellipse and mgcv are never in an @import statement), but I still get the conflict messages. John Karon From: Max Turgeon Sent: Tuesday, February 4, 2020 3:10 PM To: sierras...@mi

[R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
Thanks Duncan. Please clarify: if I use ellipse::ellipse in code, do I need to have @importFrom ellipse eliipse in the Roxygen code. -Original Message- From: Duncan Murdoch Sent: Tuesday, February 4, 2020 2:45 PM To: sierras...@mindspring.com Subject: Re: [R-pkg-devel] function name co

[R-pkg-devel] function name conflict problem

2020-02-04 Thread sierrastew
In trying to develop a package to be submitted to CRAN, when I do Install and Reload or devtools::check(), I get the warning: Warning: replacing previous import 'ellipse::pairs' by 'graphics::pairs' when loading 'karon' Warning: replacing previous import 'MVN::mvn' by 'mgcv::mvn' when loading