[Bioc-devel] What can I do if a depended package is not installed in Bioconductor build server

Hi Anh,

We don't build CRAN packages from source on the Windows and Mac builders 
but instead install the binaries. Building all CRAN packages from source 
would require installation and maintenance of many more system 
dependencies. We may decide to support this in the future but currently 
it's not done.

There is no R 3.6 El Capitan binary for devtools available which is why 
it's not installed on merida2:

   https://cran.r-project.org/web/packages/devtools/index.html

Actually none of the CRAN packages have el-capitan R 3.6 binaries yet:

   https://cran.r-project.org/bin/macosx/el-capitan/contrib/3.6/

We hope the binaries will be built soon. You could make a request for 
this on the R-SIG-MAC mailing list:

   https://stat.ethz.ch/mailman/listinfo/r-sig-mac

Valerie

Hello,

I noticed that multiple packages currently have errors because 'devtools'
was not installed on merida2. I wonder if the issue will go away eventually
or we will have to make changes to our packages to pass the check.

For my HPAanalyze package specifically, merida2 also didn't have the
XLConnect package and gave me errors. I worked around that by replacing
XLConnect with openxlsx, which was actually a positive change for my
package. However, devtools is a lot harder to replace as it is an integral
part of my package development workflow.

May you help me to understand how packages are installed in the build
servers, and what I can do to fix the problem, please?

Thank you,
Anh Tran.

	[[alternative HTML version deleted]]

_______________________________________________
Bioc-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel

This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.