Skip to content

Suggestions to simplify constructor #130

@bkreider

Description

@bkreider
  1. The "specs" key can be simplified by using a string pointing to your environment file to avoid repeating all of the packages. Unfortunately, the format is not an environment spec but a requirements.txt format. https://conda.github.io/constructor/construct-yaml/#specs

A list of package specifications; e.g. python 2.7*, pyzmq or numpy >=1.8. The specifications are identical in form and purpose to those that would be included in a conda create --file command. Packages may also be specified by an exact URL, e.g., https://repo.anaconda.com/pkgs/main/osx-64/openssl-1.0.2o-h26aff7b_0.tar.bz2. This key can also take a str pointing to a requirements file with the same syntax.

  1. Is there a reason to "keep_pkgs" and then use the post_install.sh to remove them? If not, it would be easier to remove the post_install.sh and allow the installer to remove them.
keep_pkgs: true                 <<<<<<<<<<<<<<<
license_file: LICENSE
name: radioconda
post_install: post_install.sh   <<<<<<<<<<<<<<<

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions