Add a recipe for glean-gene

[martin-g]

GLEAN is an unsupervised learning system to integrate disparate sources of gene structure evidence (gene model predictions, EST/protein genomic sequence alignments, SAGE/peptide tags, etc) to produce a consensus gene prediction, without prior training.

Describe your pull request here

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

[martin-g]

@BiocondaBot please fetch artifacts

[BiocondaBot]

Package(s) built are ready for inspection:

Arch	Package	Zip File / Repodata	CI	Instructions
noarch	glean-gene-1.0.1-hdfd78af_0.tar.bz2	noarch.zip	GitHub Actions	show You may also use conda to install after downloading and extracting the zip file. conda install -c ./packages <package name>

---

Docker image(s) built:

Package	Tag	CI	Install with docker
glean-gene	1.0.1--hdfd78af_0	GitHub Actions	show Images are in the linux-64 zip file above.gzip -dc images/glean-gene---1.0.1--hdfd78af_0.tar.gz | docker load

[martin-g]

@aliciaaevans How much work would it be to have two artifacts for the Github builds - the current Docker file and just the Conda package ?
My problem at the moment is that this simple noarch recipe produces a file with size of 1.2GB.
I'd like to test only the Conda package (few KB, that could be downloaded in few seconds).

[martin-g]

@BiocondaBot please add label

[aliciaaevans]

@martin-g In addition to changing the workflow yaml to upload separate artifact files, we'd have to make some changes to bioconda-utils to handle it for the upload to the channel when master is merged. Nothing too time-consuming, just a matter of someone getting around to it.

Changes would be in this file if you or anyone else want to take it on:
https://github.com/bioconda/bioconda-utils/blob/fcaf2913238ecf19e898da29676c7db107d1d539/bioconda_utils/artifacts.py#L31
And then the BiocondaBot artifacts comment would need to change: https://github.com/bioconda/bioconda-containers/blob/7b022b17af3f18619b629c1ee13df151c66b7fb8/images/bot/src/bioconda_bot/comment.py#L126