search for: pkgkitten

...l is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension fonts' which gets repeated a bit. I have been using latex for a long time, but I can't make heads and tails of it. Any idea? Dirk $ R CMD Rd2pdf pkgKitten ## just because I know the manual builds Hmm ... looks like a package Converting Rd files to LaTeX Creating pdf output from LaTeX ... Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'Rd2.tex' failed. LaTeX errors: ! Math f...

Mehmet, That is a loaded topic, not unlikely other topics preoccupying us these days. There is package.skeleton() in base R as you already mentioned. It drove me bonkers that it creates packages which then fail R CMD check, so I wrote a wrapper package (pkgKitten) with another helper function (kitten()) which calls the base R helper and then cleans up it---but otherwise remains faithful to it. These days pkgKitten defaults to creating per-package top-level help page that just references content from DESCRIPTION via a set of newer Rd macros as I find that h...

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can | pull the pkgKitten source down, and run R CMD Rd2pdf pkgKitten without | issue: Thank you. That is the expected behaviour and also wha...

...8-generic linux-image-4.4.0-130-generic linux-image-4.4.0-134-generic linux-image-4.4.0-137-generic linux-image-4.4.0-138-generic mailutils-common Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libquantlib0v5 littler r-cran-littler r-cran-pkgkitten r-cran-rcpp Suggested packages: r-cran-getopt r-cran-inline The following NEW packages will be installed: libquantlib0v5 littler r-cran-littler r-cran-pkgkitten r-cran-rcpp r-cran-rquantlib 0 upgraded, 6 newly installed, 0 to remove and 177 not upgraded. Need to get 11.2 MB of archives....

...c > linux-image-4.4.0-134-generic linux-image-4.4.0-137-generic > linux-image-4.4.0-138-generic mailutils-common > > Use 'sudo apt autoremove' to remove them. > > The following additional packages will be installed: > > libquantlib0v5 littler r-cran-littler r-cran-pkgkitten r-cran-rcpp > > Suggested packages: > > r-cran-getopt r-cran-inline > > The following NEW packages will be installed: > > libquantlib0v5 littler r-cran-littler r-cran-pkgkitten r-cran-rcpp > r-cran-rquantlib > > 0 upgraded, 6 newly installed, 0 to remove and 1...

...--------------------------------- goran at M6800:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: littler r-cran-littler r-cran-pkgkitten Use 'sudo apt autoremove' to remove them. ------------------------------------------------- (Why) should I remove them? Why are they 'no longer required'? G?ran

...e: > > Mehmet, > > That is a loaded topic, not unlikely other topics preoccupying us these days. > > There is package.skeleton() in base R as you already mentioned. It drove me > bonkers that it creates packages which then fail R CMD check, so I wrote a > wrapper package (pkgKitten) with another helper function (kitten()) which > calls the base R helper and then cleans up it---but otherwise remains > faithful to it. Failing R CMD check isn't a big deal: you want to be reminded to edit those incomplete help files. But I think I recall that you couldn't even...

Hello everybody, as a young/unexperienced R package developer (only a few, mainly for personal use) i was thinking it could be very useful having a "meta" task view for all package-development related packages and/or function. Something like ... Creation - utils::package.skeleton, pkgKitten, Rcpp::Rcpp.package.skeleton Foreign languages interfaces: - Rcpp Documentation - roxygen2 Profiling: - utils::Rprof - profr - proftools Unit test - RUnit - testthat Spell checking - tools::aspell_package_* functions "Misc": - devtools and so on. These are only the ones i (use or...

...> > Mehmet, > > That is a loaded topic, not unlikely other topics preoccupying us these > days. > > There is package.skeleton() in base R as you already mentioned. It drove me > bonkers that it creates packages which then fail R CMD check, so I wrote a > wrapper package (pkgKitten) with another helper function (kitten()) which > calls the base R helper and then cleans up it---but otherwise remains > faithful to it. > > These days pkgKitten defaults to creating per-package top-level help page > that just references content from DESCRIPTION via a set of newer Rd...

...ary platforms. update.packages() fails when you set options(repos). Looks like it is trying to download a tgz file from the src/contrib section of a repository (on a mac). To reproduce this you need to have an older version of AnnotationDbi installed, which I accomplished by faking it, installing pkgKitten and then doing: library(pkgKitten) kitten("AnnotationDbi") Then exiting R and doing R CMD INSTALL AnnotationDbi. Here's the problem: > packageVersion("AnnotationDbi") [1] ?1.0? > options(repos=structure(c("http://bioconductor.org/packages/3.1/bioc", &quo...

...have 56 font packages installed under CentOS 7 | locally, but then I work pretty carefully to cull them down | | What is the specific 'leaf node' package you are trying to I noticed it with a local, not-public package -- but it appears to apply with any source package. I replicated with pkgKitten straight off CRAN and after checking that it has a six page manual there. Here, I get an aborted (!!) source file, same happens with the local, non-public package: ----------------------------------------------------------------------------- \documentclass[a4paper]{book} \usepackage[times,hyper]{...

On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: > I noticed it with a local, not-public package -- but it appears to apply with > any source package. I replicated with pkgKitten straight off CRAN and after > checking that it has a six page manual there. I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can pull the pkgKitten source down, and run R CMD Rd2pdf pkgKitten without issue: [spot at localhost ~]$ tar xf pkgKitten_0.1.4.tar.gz [spot at lo...

...----------------- | goran at M6800:~$ sudo apt upgrade | Reading package lists... Done | Building dependency tree | Reading state information... Done | Calculating upgrade... Done | The following packages were automatically installed and are no longer | required: | littler r-cran-littler r-cran-pkgkitten | Use 'sudo apt autoremove' to remove them. | ------------------------------------------------- | | (Why) should I remove them? Why are they 'no longer required'? Educated guess, I am myself a little unsure here: - when installing, the dpkg / apt / ... suite now marks a package a...

>> There is package.skeleton() in base R as you already mentioned. It drove >> me >> bonkers that it creates packages which then fail R CMD check, so I wrote a >> wrapper package (pkgKitten) with another helper function (kitten()) which >> calls the base R helper and then cleans up it---but otherwise remains >> faithful to it. > > > Failing R CMD check isn't a big deal: you want to be reminded to edit those > incomplete help files. But I think I recall th...

...>> That is a loaded topic, not unlikely other topics preoccupying us these >> days. >> >> There is package.skeleton() in base R as you already mentioned. It drove me >> bonkers that it creates packages which then fail R CMD check, so I wrote a >> wrapper package (pkgKitten) with another helper function (kitten()) which >> calls the base R helper and then cleans up it---but otherwise remains >> faithful to it. >> >> These days pkgKitten defaults to creating per-package top-level help page >> that just references content from DESCRIPTION v...

Dear R developers, I am wondering what are the best practices for developing an R package. I am aware of Hadley Wickham's best practice documentation/book (http://r-pkgs.had.co.nz/). I recall a couple of years ago there were some tools for generating a package out of a single file, such as using package.skeleton, but no auto-generated documentation. Do you know a way to generate

On 30/01/2018 11:29 AM, Brian G. Peterson wrote: > On Tue, 2018-01-30 at 17:00 +0100, Suzen, Mehmet wrote: >> Dear R developers, >> >> I am wondering what are the best practices for developing an R >> package. I am aware of Hadley Wickham's best practice >> documentation/book (http://r-pkgs.had.co.nz/).??I recall a couple of >> years ago there were some