ckages/EBImage') instead of doing it for them.
>
> Martin
>
> From: Tiago Olivoto
> Date: Friday, September 3, 2021 at 2:14 PM
> To: Martin Morgan
> Cc: Uwe Ligges , R Package Devel <
> r-package-devel@r-project.org>
> Subject: Re: [R-pkg-devel] Checking pack
To: Martin Morgan
Cc: Uwe Ligges , R Package Devel
Subject: Re: [R-pkg-devel] Checking package dependencies before loading
namespace
Thanks for your response Martin,
I'm definitely thinking to use BiocManager::install("EBImage") since it is the
official suggestion of the Bioco
Thanks for your response Martin,
I'm definitely thinking to use BiocManager::install("EBImage") since it is
the official suggestion of the Bioconductor community. Anyway, I've been
learning a lot from this discussion. Thanks all!!
Best,
Tiago
Em sex., 3 de set. de 2021 às 12:58, Martin Morgan
esc
The specific repository you've chosen is not what you want to do. This will
always install EBImage from Bioconductor version 3.13, but Bioconductor version
3.13 is only relevant for R-4.1 (see
https://bioconductor.org/about/release-announcements/)
Personally, I would encourage you to follow the
Thank you, Duncan and Uwe for the suggestions.
I followed your instructions and created a function to check for EBImage
that is only called in an interactive section and, if necessary, ask the
user to install the package with install.packages("EBImage", repos="
https://bioconductor.org/packages/3.
Two more comments.
1. Note that your code only works in interactice mode, not when checking
your package as it waits infinitely for the user's choice.
2. I do not see an advantage of installing BiocManager if EBImage is
needed, the essential part is simply to select BioC as a repository to
i
People shouldn't be able to install your package unless the "hard"
dependencies are available.
If EBImage isn't essential to your package, you should make it a "soft"
dependency by listing it in Suggests and checking for it every time you
use it.
Duncan Murdoch
On 31/08/2021 3:20 p.m., Tiag
