I understand these reasons, and they certainly make sense when a
package has a big/complicated src/ directory. Perhaps one day more
developers will move the building and checking to cloud services (e.g.
I have been using Travis CI), so nobody cares about the
building/checking time spent on local ma
> Duncan Murdoch
> on Sun, 27 Oct 2013 08:56:31 -0400 writes:
> On 13-10-26 9:49 PM, Simon Urbanek wrote:
>> On Oct 25, 2013, at 12:12 PM, Yihui Xie wrote:
>>
>>> This has been asked s many times that I think it may
>>> be a good idea for R CMD check to just s
On 13-10-26 9:49 PM, Simon Urbanek wrote:
On Oct 25, 2013, at 12:12 PM, Yihui Xie wrote:
This has been asked s many times that I think it may be a good
idea for R CMD check to just stop when the user passes a directory
instead of a tar ball to it, or automatically run R CMD build before
mov
On Oct 25, 2013, at 12:12 PM, Yihui Xie wrote:
> This has been asked s many times that I think it may be a good
> idea for R CMD check to just stop when the user passes a directory
> instead of a tar ball to it, or automatically run R CMD build before
> moving on. In my opinion, sometimes an F
On 25/10/2013 11:37 AM, Sanford Weisberg wrote:
Using SUSE Linux, Windows 32 bit and Windows 64 bit R 3.0.2 , I am unable
to use R CMD check successfully. Here is the Windows 64 bit report:
Both checking and installing code are really designed to work on
tarballs, as John said. Some parts of
This has been asked s many times that I think it may be a good
idea for R CMD check to just stop when the user passes a directory
instead of a tar ball to it, or automatically run R CMD build before
moving on. In my opinion, sometimes an FAQ and a bug are not entirely
different.
Regards,
Yihui
Using SUSE Linux, Windows 32 bit and Windows 64 bit R 3.0.2 , I am unable
to use R CMD check successfully. Here is the Windows 64 bit report:
Z:\R\source\effects>R CMD check pkg
* using log directory 'Z:/R/source/effects/pkg.Rcheck'
* using R version 3.0.2 (2013-09-25)
* using platform: x86_64-w
On 22/08/2008 11:21 AM, Giles Hooker wrote:
I have a query after finding an error running Rtools on a Windows machine.
I am trying to build an update to the R fda library using Rtools27 under
Windows XP Pro. This is the current fda library on RForge:
http://r-forge.r-project.org/projects/fda
I have a query after finding an error running Rtools on a Windows machine.
I am trying to build an update to the R fda library using Rtools27 under
Windows XP Pro. This is the current fda library on RForge:
http://r-forge.r-project.org/projects/fda
Following R CMD build, R CMD check produces
Duncan Murdoch-2 wrote:
>
> On 11/22/2007 10:11 AM, Ulrike Grömping wrote:
> > Hi Duncan,
> >
> > yes, I am talking about a new version (currently called 1.99, to be
> made 2.0 on release). I don't think I should attach the file in a note
> to the list - should I ?
> >
> > I've just atta
On 11/22/2007 10:11 AM, Ulrike Grömping wrote:
> Hi Duncan,
>
> yes, I am talking about a new version (currently called 1.99, to be
made 2.0 on release). I don't think I should attach the file in a note
to the list - should I ?
>
> I've just attached the tar-file for you. Please let me know
On 11/22/2007 9:26 AM, Ulrike Grömping wrote:
> I suppose I should add that this is under Windows (XP).
> Regards, Ulrike
>
>
> Ulrike Grömping wrote:
>>
>> Dear R-developers,
>>
>> I'm experiencing a problem with having an example run under R 2.6.1 RC
>> (downloaded and installed today, r43513
I suppose I should add that this is under Windows (XP).
Regards, Ulrike
Ulrike Grömping wrote:
>
> Dear R-developers,
>
> I'm experiencing a problem with having an example run under R 2.6.1 RC
> (downloaded and installed today, r43513), which does not occur on R 2.6.0:
> The new version of pac
Dear R-developers,
I'm experiencing a problem with having an example run under R 2.6.1 RC
(downloaded and installed today, r43513), which does not occur on R 2.6.0:
The new version of package relaimpo does list package survey under
"Depends", and an example directly (i.e. not only from within a f
Joerg van den Hoff wrote:
> I tried two times to get some help for this from the help list but to no
> avail. I hope,
> it's OK to post this here (once...). if not, please ignore (the rest of) this
> mail:
>
> for one of my private packages R CMD CHECK {package} givves me annoying
> warnings
>
I tried two times to get some help for this from the help list but to no avail.
I hope,
it's OK to post this here (once...). if not, please ignore (the rest of) this
mail:
for one of my private packages R CMD CHECK {package} givves me annoying warnings
due to 'missing links' in the manpages for
This is specific to the `universal' MacOS X binary: it is saying it cannot
run the i386 executable. If this is not a i386 Mac, some variable is set
wrong. In any case, I suggest the R-sig-mac list.
On Mon, 22 May 2006, Robin Hankin wrote:
> Hi
>
> I have a package that I'm testing.
> It seems
Hi
I have a package that I'm testing.
It seems to install fine and it works, as far as I can tell.
For example, I can install the package, and use it,
and source the test suite with no errors.
My problem is with R CMD check.
It passes on R-2.2-0:
Robin-Hankins-Computer:~/scratch% R CMD check
18 matches
Mail list logo
