Package status reports come in three different severities: NOTE, WARNING, and
ERROR. Motivated by Brodie's nice (dependency-free) accessor function for
per-maintainer status [1], I have looked into reducing the number of ERRORs.
I hit a road block. Several of my packages depend on external libr
On 04.09.2018 04:18, David B. Dahl wrote:
I would like advise and help in interpreting a part of the CRAN
Repository Policy. It states, "Downloads of additional software or
data as part of package installation or startup should only use secure
download mechanisms (e.g., ‘https’ or ‘ftps’)."
On 04.09.2018 16:36, Dirk Eddelbuettel wrote:
Package status reports come in three different severities: NOTE, WARNING, and
ERROR. Motivated by Brodie's nice (dependency-free) accessor function for
per-maintainer status [1], I have looked into reducing the number of ERRORs.
I hit a road blo
On 4 September 2018 at 17:07, Uwe Ligges wrote:
| Disclaimer for this field in general (as others are listening, too): we
| should always try not to use it alt all and produce cross platform code.
It would be nice if the CRAN system was more open so that contributed builds
could be used. With m
Uwe: Oh, right, I wasn't thinking about binary packages. Thanks! -- David
On Tue, Sep 4, 2018 at 9:02 AM Uwe Ligges
wrote:
>
>
>
> On 04.09.2018 04:18, David B. Dahl wrote:
> > I would like advise and help in interpreting a part of the CRAN
> > Repository Policy. It states, "Downloads of addit
