:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'bioconductor-basilisk.utils' .. highlight: bash bioconductor-basilisk.utils =========================== .. conda:recipe:: bioconductor-basilisk.utils :replaces_section_title: :noindex: Basilisk Installation Utilities :homepage: https://bioconductor.org/packages/3.18/bioc/html/basilisk.utils.html :license: GPL-3 :recipe: /`bioconductor-basilisk.utils `_/`meta.yaml `_ Implements utilities for installation of the basilisk package\, primarily for creation of the underlying Conda instance. This allows us to avoid re\-writing the same R code in both the configure script \(for centrally administered R installations\) and in the lazy installation mechanism \(for distributed package binaries\). It is highly unlikely that developers \- or\, heaven forbid\, end\-users\! \- will need to interact with this package directly\; they should be using the basilisk package instead. .. conda:package:: bioconductor-basilisk.utils |downloads_bioconductor-basilisk.utils| |docker_bioconductor-basilisk.utils| :versions: ``1.14.1-0``,  ``1.12.1-0``,  ``1.10.0-0``,  ``1.6.0-0``,  ``1.4.0-0``,  ``1.2.2-0``,  ``1.2.0-0``,  ``1.0.0-0`` :depends bioconductor-dir.expiry: ``>=1.10.0,<1.11.0`` :depends r-base: ``>=4.3,<4.4.0a0`` :requirements: .. rubric:: Installation You need a conda-compatible package manager (currently either `micromamba `_, `mamba `_, or `conda `_) and the Bioconda channel already activated (see :ref:`set-up-channels`). While any of above package managers is fine, it is currently recommended to use either micromamba or mamba (see `here `_ for installation instructions). We will show all commands using mamba below, but the arguments are the same for the two others. Given that you already have a conda environment in which you want to have this package, install with:: mamba install bioconductor-basilisk.utils and update with:: mamba update bioconductor-basilisk.utils To create a new environment, run:: mamba create --name myenvname bioconductor-basilisk.utils with ``myenvname`` being a reasonable name for the environment (see e.g. the `mamba docs `_ for details and further options). Alternatively, use the docker container:: docker pull quay.io/biocontainers/bioconductor-basilisk.utils: (see `bioconductor-basilisk.utils/tags`_ for valid values for ````) .. |downloads_bioconductor-basilisk.utils| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-basilisk.utils.svg?style=flat :target: https://anaconda.org/bioconda/bioconductor-basilisk.utils :alt: (downloads) .. |docker_bioconductor-basilisk.utils| image:: https://quay.io/repository/biocontainers/bioconductor-basilisk.utils/status :target: https://quay.io/repository/biocontainers/bioconductor-basilisk.utils .. _`bioconductor-basilisk.utils/tags`: https://quay.io/repository/biocontainers/bioconductor-basilisk.utils?tab=tags .. raw:: html Download stats ----------------- .. raw:: html :file: ../../templates/package_dashboard.html Link to this page ----------------- Render an |install-with-bioconda| badge with the following MarkDown:: [![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/bioconductor-basilisk.utils/README.html) .. |install-with-bioconda| image:: https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat :target: http://bioconda.github.io/recipes/bioconductor-basilisk.utils/README.html