On 13-10-20 04:58 PM, Gabor Grothendieck wrote:
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
wrote:
On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
I'm working on an update for my CRAN package "spatial.tools" and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN
On 13-10-20 6:41 PM, Jonathan Greenberg wrote:
To be clear, if I used Depends: somepackage before, and switched over to
using Imports: somepackage, I'll need to mod my code that used to have a
call to, say, somefunction to now have somepackage::somefunction, correct?
No. You need to modify bot
Jonathan,
import/importFrom directives within the NAMESPACE places the symbol(s)
within your package's namespace. They are treated exactly the same as
(non-exported) symbols your code defines.
~G
On Sun, Oct 20, 2013 at 3:41 PM, Jonathan Greenberg wrote:
> To be clear, if I used Depends: somep
On 13-10-20 4:54 PM, Jonathan Greenberg wrote:
Duncan:
Thanks -- learning something new today -- quick follow-up, will using
the import statements in the NAMESPACE, when a user goes to
install.packages(), auto-install the "dependent" packages the same way
Depends forces?
You need to list the
To be clear, if I used Depends: somepackage before, and switched over to
using Imports: somepackage, I'll need to mod my code that used to have a
call to, say, somefunction to now have somepackage::somefunction, correct?
--j
On Sun, Oct 20, 2013 at 5:34 PM, Dirk Eddelbuettel wrote:
>
> On 20 O
On 20 October 2013 at 16:20, Jonathan Greenberg wrote:
| One more follow-up -- will I now need to include a library() statement in
| each function?
No.
NAMESPACE entry, coupled with Imports: in DESCRIPTION.
Dirk
--
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
__
One more follow-up -- will I now need to include a library() statement in
each function?
--j
On Sun, Oct 20, 2013 at 3:58 PM, Gabor Grothendieck wrote:
> On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
> wrote:
> > On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
> >>
> >> I'm working on an upd
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
wrote:
> On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
>>
>> I'm working on an update for my CRAN package "spatial.tools" and I noticed
>> a new warning when running R CMD CHECK --as-cran:
>>
>> * checking CRAN incoming feasibility ... NOTE
>> Maint
Duncan:
Thanks -- learning something new today -- quick follow-up, will using the
import statements in the NAMESPACE, when a user goes to install.packages(),
auto-install the "dependent" packages the same way Depends forces?
--j
On Sun, Oct 20, 2013 at 3:49 PM, Duncan Murdoch wrote:
> On 13-10
On 13-10-20 4:43 PM, Jonathan Greenberg wrote:
I'm working on an update for my CRAN package "spatial.tools" and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Jonathan Asher Greenberg '
Depends: includes the non-default pack
I'm working on an update for my CRAN package "spatial.tools" and I noticed
a new warning when running R CMD CHECK --as-cran:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Jonathan Asher Greenberg '
Depends: includes the non-default packages:
'sp' 'raster' 'rgdal' 'mmap' 'abind' 'par
11 matches
Mail list logo
