Hi Martin,
Thanks for the heads-up. I think I've made the changes necessary, but am
having trouble confirming whether the changes are correct on a Windows
machine.
Could you tell me hows Bioconductor builds the Windows binaries of
Bioconductor packages?
To see how things work, I am
The subversion log for 2013 (http://developer.r-project.org/R_svnlog_2013) on
the R developer page hasn't been updated since September 29. I would
appreciate the daily updates returning.
Berend Hasselman
__
R-devel@r-project.org mailing list
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 spatial-to...@estarcion.net'
Depends: includes the non-default packages:
'sp' 'raster'
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 spatial-to...@estarcion.net'
Depends:
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
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
murdoch.dun...@gmail.com 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 ...
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 ggrothendi...@gmail.com
wrote:
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
murdoch.dun...@gmail.com wrote:
On 13-10-20 4:43 PM, Jonathan
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
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 e...@debian.org
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
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 j...@illinois.eduwrote:
To be clear, if I
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
On 13-10-20 04:58 PM, Gabor Grothendieck wrote:
On Sun, Oct 20, 2013 at 4:49 PM, Duncan Murdoch
murdoch.dun...@gmail.com 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
Jai,
On Oct 19, 2013, at 1:37 AM, JaiReddy wrote:
Thanks Simon.
May I know how R works if two expressions come at the same time for
evaluation. When I debug my case I found that issue was found with indexed
values of protected items.
As R is single threaded engine, I just want to know
On Oct 20, 2013, at 2:00 AM, Berend Hasselman wrote:
The subversion log for 2013 (http://developer.r-project.org/R_svnlog_2013) on
the R developer page hasn't been updated since September 29. I would
appreciate the daily updates returning.
Sorry, my bad, with all the server switching I
On 21-10-2013, at 03:38, Simon Urbanek simon.urba...@r-project.org wrote:
On Oct 20, 2013, at 2:00 AM, Berend Hasselman wrote:
The subversion log for 2013 (http://developer.r-project.org/R_svnlog_2013)
on the R developer page hasn't been updated since September 29. I would
appreciate
16 matches
Mail list logo
