Sounds like a good proposal, but currently this is not implemented.
Best,
Uwe Ligges
On 22.07.2015 01:10, François Michonneau wrote:
Hello all,
As I can only easily access computers with Linux, I am very grateful
for the existence of win-builder to test my packages with Windows.
Today
Hello all,
As I can only easily access computers with Linux, I am very grateful
for the existence of win-builder to test my packages with Windows.
Today I encountered an issue with win-builder that took me a while
to figure out. My package was failing unit tests on win-builder but I
couldn't
Probably I'm too distrustful, but yesterday I tried to use Travis CI
and at the end I didn't do it, because of the permissions you're
requested to give to the application:
Review permissions:
Personal user data : Email addresses (read-only)
Repository webhooks and services
On 21/07/2015 2:08 PM, Jennifer Bryan wrote:
> Sebastien: thanks for sharing the definitive solution!
>
> To the people on this list with the power to edit "Writing R Extensions":
>
> When a discussion here suggests a specific improvement, what is the best way
> for the community to propose a re
Sebastien: thanks for sharing the definitive solution!
To the people on this list with the power to edit "Writing R Extensions":
When a discussion here suggests a specific improvement, what is the best way
for the community to propose a revision? So that knowledge gets transferred
from this lis
On Tue, Jul 21, 2015 at 2:35 PM, Gavin Simpson wrote:
> Perhaps I have missed some detail, but would Gabor Csardi's r-builder code
> not provide this (or something close to it) for Linux at least? See:
> https://github.com/metacran/r-builder
It does, although it only does Ubuntu 12.04 if you use
Perhaps I have missed some detail, but would Gabor Csardi's r-builder code
not provide this (or something close to it) for Linux at least? See:
https://github.com/metacran/r-builder
This builds on the R support for Travis CI, and allows for testing against
R-release and R-devel (plus R-oldrelease
On 21 July 2015 at 11:46, Duncan Murdoch wrote:
> On 21/07/2015 9:01 AM, ProfJCNash wrote:
>>
>> There has been some disagreement on where it is appropriate to post
>> questions about package checking procedures, including the building of
>> the environment e.g., R-devel under Linux Mint.
>>
>> In
On 21/07/2015 9:01 AM, ProfJCNash wrote:
>
> There has been some disagreement on where it is appropriate to post
> questions about package checking procedures, including the building of
> the environment e.g., R-devel under Linux Mint.
>
> In looking at https://www.r-project.org/mail.html, it see
There has been some disagreement on where it is appropriate to post
questions about package checking procedures, including the building of
the environment e.g., R-devel under Linux Mint.
In looking at https://www.r-project.org/mail.html, it seems to me that
the procedures belong with r-package-de
Hi Jennifer,
Following your suggestions and after a couple of trial-and-error steps,
I believe the syntax is the following:
\code{\link[name_of_package:name_of_Rd_file]{alias_or_text}}
For instance, to link to panel.abline or strip.custom from the lattice
package, I used:
\code{\link[latti
> On 21 Jul 2015, at 08:12 , Johannes Ranke wrote:
>
>>>
>>> Could you guys move to r-devel? This has nothing to do with _package_
>>> development.
>
> OK, the details of how to configure a build are maybe a bit too far off...
> But
> in general, testing with a recent development build is an
12 matches
Mail list logo
