quiet and verbose options to install2r

[zivankaraman]

I often build rocker-based images, which require installing many R packages, many of which require compilation. With the default installation options, this can produce very, very long log files that are impractical. The ‘quiet’ and ‘verbose’ options to ‘install2r’ that I added allow for fine-tuning the output quantity.
Please let me know if you require any additional details or clarification regarding these changes.

[eddelbuettel]

You could also use r2u to skip the compilation step - - that is my preferred approach.

Will take a peek at the PR when I get a moment, currently away from keyboards.

[eddelbuettel]

Also, do you have a (small, pererably) package where your PR shows a difference in installation 'noise'?

(I have also been thinking to add default compiler flags to make eg RcppEigen-using compilation more quiet...)

[eddelbuettel]

I am now (briefly) at my laptop. This may be the wrong repo to report this too -- install2.r is a script that is part of the littler repo (I maintain) so you should maybe try it there. As I often suggest, starting with an issue to discuss aspects may be preferable to just trying a PR. But that may just be my preference.

[zivankaraman]

Thank you for your comments. My use case stemmed from building a rocker-based Docker image, so I modified the install2r included in the rocker repo. I will follow your suggestions.

[eddelbuettel]

Sounds good. We can continue the discussion over at the littler repo. Passing quiet and verbose down to install.packages() is a good idea in general. I will try and see (maybe in a container) to see what effect it has. If you have some specific packages where it helps / illustrates this best with let me know as it may help me appreciate this more fully 😉

[eitsupi]

Please consider adding it here as well when it is updated in littler.

As @zivankaraman guessed, it is the forked version here that is actually used in the image (we always include the latest version in the repository, since the littler package in the image may not be the latest version. Also, this forked version has additional features, too, that might be worth adding to upstream)

[eddelbuettel]

Yes, and coincidentally I just made essentially the same comment in a reply to the littler issue just opened by @zivankaraman (and before I saw this). We may want this here locally "in the meantime" and we want it "eventually as well" upstream so that it bubbles through the CRAN package process too.