Package Recipe 'bioconductor-biodbexpasy'

recipe bioconductor-biodbexpasy

biodbExpasy, a library for connecting to Expasy ENZYME database.

Homepage:: https://bioconductor.org/packages/3.18/bioc/html/biodbExpasy.html
License:: AGPL-3
Recipe:: /bioconductor-biodbexpasy/meta.yaml

The biodbExpasy library provides access to Expasy ENZYME database, using biodb package framework. It allows to retrieve entries by their accession number. Web services can be accessed for searching the database by name or comments.

package bioconductor-biodbexpasy¶

Versions:

1.6.0-0, 1.4.0-0, 1.2.0-0

Depends:

on bioconductor-biodb >=1.10.0,<1.11.0
on r-base >=4.3,<4.4.0a0
on r-chk
on r-r6
on r-stringr

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-biodbexpasy

to add into an existing workspace instead, run:

pixi add bioconductor-biodbexpasy

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-biodbexpasy

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-biodbexpasy

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-biodbexpasy:<tag>

(see bioconductor-biodbexpasy/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:

[![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/bioconductor-biodbexpasy/README.html)