[Bioc-devel] external dependencies

Anna Gogleva gogleva.a.a at gmail.com
Mon Oct 2 11:36:57 CEST 2017

Dear Bioconductor Team,

I have written a package and was planning to submit it to Bioconductor one
day. The package provides a set of wrapper functions around several
existing command line tools to construct scalable and reproducible
pipelines for secretome prediction.

The package requires several external system dependencies to be installed
in order to work (listed in the SystemRequirements filed). I have a
top-level README describing in detail how to install the required
dependencies and a shell script to automate this process. The thing is,
some of the external dependencies were not designed to work on Windows -
causing certain unit tests and examples to fail during the automatic R CMD
check on Windows.

I have run R CMD check on Mac and Linux and the package passes without
errors, warnings or notes. It also satisfies the remaining requirements
from the recommended package checklist.

What would be the best way to proceed? Would it be still ok to submit the
package though it is not fully functional on Windows due to unavailability
of certain external dependencies?

Thank you for your advice,

Anna Gogleva

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list