Hi Ott,
There is no documented way to detect whether you are running on CRAN. So
there is nothing to rely on, on that side.
You can only make your own machine detectable by the test code. For example
by setting an environment variable that identifies your machine and make
test execution depend
Dear Richel,
The comment itself is pretty clear I think: to be accepted on CRAN you
should not use testthat tests in your examples.
I can't speak for CRAN but I'm pretty convinced this is for testing in
general.
Tests are for testing, not for demonstration. Most users of your package
will
Adding a static PDF vignette is very easy. I have written about it here:
http://www.markvanderloo.eu/yaRb/2019/01/11/add-a-static-pdf-vignette-to-an-r-package/
Best,
Mark
Op vr 25 okt. 2019 13:22 schreef Berry Boessenkool <
berryboessenk...@hotmail.com>:
>
> You could also consider a static
At the cost of some level of reproducibility, you could use a static
vignette and be very clear about the package versions used in the
comparisons:
http://www.markvanderloo.eu/yaRb/2019/01/11/add-a-static-pdf-vignette-to-an-r-package/
As this does diminish the coherence of CRAN somewhat I'm not
For what it's worth,
I recently submitted a new package that was initially refused (with
comments) by CRAN. I updated number of them accordingly, but there were a
few that with good reasons I could not change. I explained this in the
comments when uploading a new version and it got accepted. So I
Dear Aditya,
You ask:
| Am I able to submit this without Windows support, or could somebody help
us with supporting Windows?
The CRAN policy[1] is pretty clear about this:
"Package authors should make all reasonable efforts to provide
cross-platform portable code. Packages will not normally
), even during the development stages. Can
> you comment? Thanks.
>
> -- Mike
>
>
> On Tue, Jul 17, 2018 at 2:53 AM, Mark van der Loo
> wrote:
> > Michael,
> >
> > Just a small side-track here. I would avoid using the not-a-pipe operator
> > with
Michael,
Just a small side-track here. I would avoid using the not-a-pipe operator
within functions or packages in general. It is great for interactive use,
but it does make debugging and hence long-term maintenance of functions
harder. There are two reasons for this. First, it hides intermediate
Hi Alejandro,
Brooke Anderson gave a nice talk at useR!2017 addressing this exact issue.
See
https://schd.ws/hosted_files/user2017/19/anderson-eddelbuettel-use_r_talk.pdf
for
the slides. The basic idea is to use an external CRAN-like repository for
the data back-end. Brooke used 'drat' to set up
Dear Vincent,
I think this is little known, but you can get the CRAN result status of any
package from R, see tools::CRAN_check_results().
Best,
Mark
Op ma 25 jun. 2018 om 22:13 schreef Duncan Murdoch :
> On 25/06/2018 3:21 PM, Vincent van Hees wrote:
> > Dear all,
> >
> > One of my package
Knut
AFAIR the download statistics are limited to downloads from RStudio's cloud
service, so none of the other CRAN mirrors are included. I think there is
no separation between updates, re-installs, or installs done automatically
by CI-services, for example.
-Mark
Op vr 16 mrt. 2018 om 12:30
Dear Hugh, this question was asked earlier on this list:
http://r.789695.n4.nabble.com/executable-files-R-package-td4390488.html
See especially the answer of Duncan Murdoch.
Best,
Mark
Op di 9 jan. 2018 om 03:26 schreef Hugh Parsonage :
> On
Dear Robert,
R supports package repositories out of the box. A repository is just a way
of organizing files. The most popular repositories are CRAN and
Bioconductor. There is even a package that allows you to set up your own
repository on Github (the drat package).
It depends on the repository
You could first have a look at the LaF packge. It does a lot of what you
want already.
-M
Op zo 17 sep. 2017 om 04:41 schreef Juan Telleria :
> Dear R Developers,
>
> I am writing as I would like to propose a github project for the creation
> of on-disk data.frames/tibbles.
I have had no problems recently (having updated a pkg or two with this over
the last couple of weeks). Your question is not reproducible so its hard to
help...
best,
Mark
Op wo 21 jun. 2017 om 23:46 schreef Simon Barthelmé <
simon.barthe...@gipsa-lab.fr>:
> Dear list,
>
> Is anybody else having
I had the same experience. Also recently I uploaded a pkg without a
vignette but with a vignette engine specified in the DESCRIPTION. This
gave no error with R CMD check --as-cran (r-dev) but I did receive a
request to fix it.
-M
On Tue, Jun 20, 2017, 17:50 Thomas J. Leeper
Julia,
Just took the poll.
I think cranberries would deserve mention there as well. It is the only
continuous feed that reports in new pkgs and updates (that I know of).
Best,
Mark
On Mon, Mar 20, 2017, 14:57 Julia Silge wrote:
> I am contributing to a session at userR
Fwiw, there's also something called the awesome lists (
https://github.com/sindresorhus/awesome, and see the R list here:
https://github.com/qinwf/awesome-R), which is basically a kind of task
views for any language, and controlled via git pull requests.
Not sure if this would be a good
mpiling
with gcc <= 4.6.x
Best,
Mark
Op do 25 aug. 2016 om 14:44 schreef Uwe Ligges <
lig...@statistik.tu-dortmund.de>:
>
>
> On 25.08.2016 13:14, Mark van der Loo wrote:
> > Thank you Peter, good points.
> >
> > Good to know for sure (or a.s.) that c
Dear listers,
Compilation of my gower pkg fails on R-oldrel-windows. I am pretty sure
that this is because it uses gcc 4.6.3 which has limited support for OpenMP
(the errors are the same as I got on the old travis-ci build environment,
see my related question[1]).
Now, according to the Rtools
org>:
>
> On 3 August 2016 at 08:13, Mark van der Loo wrote:
> | Dear pkg developers,
> |
> |
> | I'm working on a package using C code and openMP. The package builds and
> | tests fine on my own machine[1] and also on r-hub[2]. However on
> travis-ci
> | the build cras
After reading the link in Dirk's initial reply, how about adding
fields 'Recommends'
and 'Build-Depends' to DESCRIPTION as in Debian?
Recommends: only gets installed, can be used via if(requireNamespace())
from the package and in pkg tests[1]. [Debian: The Recommends field should
list packages
Dear pkg developers,
I'm working on a package using C code and openMP. The package builds and
tests fine on my own machine[1] and also on r-hub[2]. However on travis-ci
the build crashes[3] with the following message (plus a few similar):
gower.c:297:29: error: expected ‘+’, ‘*’, ‘-’, ‘&’, ‘^’,
Mail the CRAN team.
On Wed, Jun 1, 2016, 10:24 Dean Attali wrote:
> My package 'ddpcr' was accepted into CRAN in 2016-02-19 and then updated on
> 2016-03-17. There were no errors or warnings or notes in my submission and
> it was accepted right away.
>
> I just tried going
.
Supplying binaries seems the only option unless clang developers decide to
support OpenMP, which seems unlikely since Apple wants to promote its own
parallel computing tools.
Michael Neale
mcne...@mac.com
On Aug 24, 2015, at 3:38 PM, Mark van der Loo mark.vander...@gmail.com
wrote:
At least
Berry,
why not use
\href{[your link]}{[link text]}
in the documentation details[1]?
Best,
Mark
[1] https://cran.r-project.org/doc/manuals/R-exts.html#Marking-text
Op di 18 aug. 2015 om 13:21 schreef Duncan Murdoch murdoch.dun...@gmail.com
:
On 18/08/2015 6:12 AM, Berry Boessenkool wrote:
26 matches
Mail list logo