text: user14913: In a custom package which imports a package from Bioconductor, what is the right DESCRIPTION file?
  I added in my DESCRIPTION a line with Remote like so
  Remotes: 
      bioc::3.14/dada2
   
  
  as suggested by https://cran.r-project.org/web/packages/remotes/index.html vignette, but it still failed the R check() with error "Packages required not available". I am very confused about what is the right way to solve this problem, since multiple sources propose a different solution:
  
  https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Package-Dependencies mention Additional_repository key in the DESCRIPTION
  
  mention Remotes, suggesting one add a Remotes entry to DESCRIPTION with a specific syntax for Bioconductor dependencies
  
  The following post suggest using blockViews R package development: How does one automatically install Bioconductor packages upon package installation?
  
  
  What is the appropriate way to declare dependencies on packages on Bioconductor? The remotes support helped me satisfy a dependency on a package from Github, but not for bioconductor
  
  user48: As I answered on the linked question, the right way to declare packages from repositories recognized by R is to just declare normally on the Imports, Depends, Enhances and LinkingTo.
  Bioconductor is an accepted repository so it doesn't need to be added on Additional_repository field.
  BiocViews is a required field from Bioconductor. As CRAN accepts other fields on the DESCRIPTION it could be used by CRAN packages.
  You don't mention it but if you found this problem and it wasn't on your computer were you are developing the package it means you are using a continuous integration test. The problem with CI like Github actions, travis, appveyor or other is that dependencies must be installed before (as they should on your computer).
  To install these dependencies before that depends on the CI you use and the strategy used there (install from ppa, use RSPM, use bspm::install, ...) . However, I recommend to do it via BiocManager::install because this way you can install all packages from both CRAN and Bioconductor and their dependencies.
  Even if the package is on CRAN, github or just Bioconductor with BiocManager::install you'll be able to install all the dependencies and continue to check your package normally on the CI.
  
  Additional_repositories is for other non standard repositories like a personal one or other a specific of a project. It is used by only ~100  packages of the 18765 packages on CRAN. But there are many more dependencies from CRAN to Bioconductor (and vice versa) .
  
original_text: 14913: <p>In a custom package which imports a package from Bioconductor, what is the right DESCRIPTION file?</p>
  <p>I added in my DESCRIPTION a line with Remote like so</p>
  <pre><code>Remotes: 
      bioc::3.14/dada2
   
  </code></pre>
  <p>as suggested by <a href="https://cran.r-project.org/web/packages/remotes/index.html" rel="nofollow noreferrer">https://cran.r-project.org/web/packages/remotes/index.html</a> vignette, but it still failed the R <code>check()</code> with error &quot;Packages required not available&quot;. I am very confused about what is the right way to solve this problem, since multiple sources propose a different solution:</p>
  <ul>
  <li><p><a href="https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Package-Dependencies" rel="nofollow noreferrer">https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Package-Dependencies</a> mention Additional_repository key in the DESCRIPTION</p>
  </li>
  <li><p>mention Remotes, suggesting one add a Remotes entry to DESCRIPTION with a specific syntax for Bioconductor dependencies</p>
  </li>
  <li><p>The following post suggest using blockViews <a href="https://bioinformatics.stackexchange.com/questions/3365/r-package-development-how-does-one-automatically-install-bioconductor-packages/3375#3375">R package development: How does one automatically install Bioconductor packages upon package installation?</a></p>
  </li>
  </ul>
  <p>What is the appropriate way to declare dependencies on packages on Bioconductor? The remotes support helped me satisfy a dependency on a package from Github, but not for bioconductor</p>
   48: <p>As <a href="https://bioinformatics.stackexchange.com/a/18374/48">I answered</a> on the linked question, the right way to declare packages from repositories recognized by R is to just declare normally on the Imports, Depends, Enhances and LinkingTo.</p>
  <p>Bioconductor is an accepted repository so it doesn't need to be added on Additional_repository field.
  BiocViews is a required field from Bioconductor. As CRAN accepts other fields on the DESCRIPTION it could be used by CRAN packages.</p>
  <p>You don't mention it but if you found this problem and it wasn't on your computer were you are developing the package it means you are using a continuous integration test. The problem with CI like Github actions, travis, appveyor or other is that dependencies must be installed before (as they should on your computer).</p>
  <p>To install these dependencies before that depends on the CI you use and the strategy used there (install from ppa, use RSPM, use <code>bspm::install</code>, ...) . However, I recommend to do it via <code>BiocManager::install</code> because this way you can install all packages from both CRAN and Bioconductor and their dependencies.</p>
  <p>Even if the package is on CRAN, github or just Bioconductor with <code>BiocManager::install</code> you'll be able to install all the dependencies and continue to check your package normally on the CI.</p>
  <hr />
  <p>Additional_repositories is for other non standard repositories like a personal one or other a specific of a project. It is used by only ~100  packages of the 18765 packages on CRAN. But there are many more dependencies from CRAN to Bioconductor (and vice versa) .</p>
  