- recipe bioconductor-biocbaseutils
General utility functions for developing Bioconductor packages
- Homepage:
https://bioconductor.org/packages/3.20/bioc/html/BiocBaseUtils.html
- License:
Artistic-2.0
- Recipe:
The package provides utility functions related to package development. These include functions that replace slots, and selectors for show methods. It aims to coalesce the various helper functions often re-used throughout the Bioconductor ecosystem.
- package bioconductor-biocbaseutils¶
- Versions:
1.12.0-0,1.8.0-0,1.4.0-0,1.2.0-0,1.0.0-0- Depends:
on r-base
>=4.5,<4.6.0a0
- Additional platforms:
Installation¶
You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). Below, we show how to install with either pixi or conda (for micromamba and mamba, commands are essentially the same as with conda).
Pixi¶
With pixi installed and the Bioconda channel set up (see Usage), to install globally, run:
pixi global install bioconductor-biocbaseutils
to add into an existing workspace instead, run:
pixi add bioconductor-biocbaseutils
In the latter case, make sure to first add bioconda and conda-forge to the channels considered by the workspace:
pixi workspace channel add conda-forge
pixi workspace channel add bioconda
Conda¶
With conda installed and the Bioconda channel set up (see Usage), to install into an existing and activated environment, run:
conda install bioconductor-biocbaseutils
Alternatively, to install into a new environment, run:
conda create -n envname bioconductor-biocbaseutils
with envname being the name of the desired environment.
Container¶
Alternatively, every Bioconda package is available as a container image for usage with your preferred container runtime. For e.g. docker, run:
docker pull quay.io/biocontainers/bioconductor-biocbaseutils:<tag>
(see bioconductor-biocbaseutils/tags for valid values for <tag>).
Integrated deployment¶
Finally, note that many scientific workflow management systems directly integrate both conda and container based software deployment. Thus, workflow steps can be often directly annotated to use the package, leading to automatic deployment by the respective workflow management system, thereby improving reproducibility and transparency. Check the documentation of your workflow management system to find out about the integration.
Download stats¶
Link to this page¶
Render an 
badge with the following MarkDown:
[](http://bioconda.github.io/recipes/bioconductor-biocbaseutils/README.html)
