Skip to content

[R-pkg-devel] function name conflict problem

3 messages · sierr@stew m@iii@g oii mi@dspri@g@com, Max Turgeon

#
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 <murdoch.duncan at gmail.com> 
Sent: Tuesday, February 4, 2020 2:45 PM
To: sierrastew at mindspring.com
Subject: Re: [R-pkg-devel] function name conflict problem

If you call it via ellipse::ellipse, you don't need to mention it in NAMESPACE.

I can't tell what's going wrong in your NAMESPACE file, but that's where the problem is that leads to the errors you saw.

In future, please don't write privately, post to the list.

Duncan Murdoch
On 04/02/2020 4:40 p.m., sierrastew at mindspring.com wrote:
#
I find it's well explained in the book by Hadley Wickham: http://r-pkgs.had.co.nz/namespace.html#imports


If package ellipse is in Imports (in your DESCRIPTION file), then install.packages will make sure it's available on the user's system when installing your own package. Therefore you can write ellipse::ellipse without requiring importFrom(ellipse,ellipse) in your NAMESPACE.


Max Turgeon
Assistant Professor
Department of Statistics
Department of Computer Science
University of Manitoba
maxturgeon.ca<http://maxturgeon.ca>
#
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 <Max.Turgeon at umanitoba.ca> 
Sent: Tuesday, February 4, 2020 3:10 PM
To: sierrastew at mindspring.com; r-package-devel at r-project. org
<r-package-devel at r-project.org>
Subject: Re: [R-pkg-devel] function name conflict problem

 

I find it's well explained in the book by Hadley Wickham:
<http://r-pkgs.had.co.nz/namespace.html#imports>
http://r-pkgs.had.co.nz/namespace.html#imports

 

If package ellipse is in Imports (in your DESCRIPTION file), then
install.packages will make sure it's available on the user's system when
installing your own package. Therefore you can write ellipse::ellipse
without requiring importFrom(ellipse,ellipse) in your NAMESPACE.

 

Max Turgeon
Assistant Professor

Department of Statistics
Department of Computer Science
University of Manitoba

 <http://maxturgeon.ca> maxturgeon.ca

 

  _____  

From: R-package-devel <r-package-devel-bounces at r-project.org
<mailto:r-package-devel-bounces at r-project.org> > on behalf of
sierrastew at mindspring.com <sierrastew at mindspring.com
<mailto:sierrastew at mindspring.com> >
Sent: February 4, 2020 3:48:16 PM
To: r-package-devel at r-project. org
Subject: [R-pkg-devel] function name conflict problem 

 

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 < <mailto:murdoch.duncan at gmail.com>
murdoch.duncan at gmail.com> 
Sent: Tuesday, February 4, 2020 2:45 PM
To:  <mailto:sierrastew at mindspring.com> sierrastew at mindspring.com
Subject: Re: [R-pkg-devel] function name conflict problem

If you call it via ellipse::ellipse, you don't need to mention it in
NAMESPACE.

I can't tell what's going wrong in your NAMESPACE file, but that's where the
problem is that leads to the errors you saw.

In future, please don't write privately, post to the list.

Duncan Murdoch

On 04/02/2020 4:40 p.m.,  <mailto:sierrastew at mindspring.com>
sierrastew at mindspring.com wrote:
commands from NAMESPACE.  Also, when I use the function ellipse, I code it
as ellipse::ellipse; similarly for using in.out.  I don't see any request
for anything but ellipse from the package ellipse, and in.out from mgcv:
murdoch.duncan at gmail.com>
r-package-devel at r-project. org
sierrastew at mindspring.com wrote:
your NAMESPACE file (derived from some comment in your code by roxygen2) is
importing ellipse::pairs, even though you say you don't want to do that.
You should fix that.
in NAMESPACE.
______________________________________________
 <mailto:R-package-devel at r-project.org> R-package-devel at r-project.org
mailing list
 <https://stat.ethz.ch/mailman/listinfo/r-package-devel>
https://stat.ethz.ch/mailman/listinfo/r-package-devel