Skip to content
tool for creating installers from conda packages
Branch: master
Clone or download
Latest commit 16b5021 Mar 8, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
constructor Fast uninstall Mar 7, 2019
examples add example for OSX package with post_install script Feb 25, 2019
scripts Add blacklist for run_examples Mar 7, 2019
.coveragerc Add CI testing for Travis and Appveyor Nov 14, 2017
.gitignore Remove swap file added accidentally May 19, 2018
.travis.yml Fix CI Mar 7, 2019
CHANGELOG.txt Update CHANGELOG for 2.3.0 Nov 9, 2018
CONSTRUCT.md
LICENSE.txt Update references to Anaconda, repo URLs May 20, 2018
Makefile Move doc generation out of the source code and use jinja2 Apr 3, 2018
README.md Add note for minimum required conda version Sep 30, 2018
appveyor.yml Fix CI Mar 7, 2019
codecov.yml Add CI testing for Travis and Appveyor Nov 14, 2017
setup.py author change to Anaconda Inc May 23, 2018

README.md

(conda) constructor

Build status

Build Status Build status codecov

Description:

constructor is a tool which allows constructing an installer for a collection of conda packages. Basically, it creates an Anaconda-like installer consisting of conda packages. This tool was previously proprietary and known as cas-installer.

Installation:

constructor can be installed into the base environment using:

$ conda install constructor

Once installed, the constructor command will be available:

$ constructor -h

Usage:

The constructor command takes an installer specification directory as its argument. This directory needs to contain a file construct.yaml, which specifies the name of the installer, the conda channels to pull packages from, the conda packages included in the installer etc. . The complete list of keys in this file can be found in CONSTRUCT.md. Also, the directory may contain some additional optional files (such as a license file, and image files for the Windows installer). An example is located in examples/maxiconda.

Notes:

  • Constructor does not work with noarch-Python packages. All conda packages must be available for the platform you are building the installer for.
  • An installer created by constructor does not need to include conda itself. If you require the ability to use conda after installation, add conda to the package list.
  • An installer created by constructor is not the same as Miniconda. All packages you want to include in the installer need to be listed explicitly. In particular, on Windows this means that if you want the "Anaconda Prompt", you will have to list console_shortcut, as well as menuinst.
  • For Windows builds, add the Anaconda channel /msys2 to the file constructor.yaml. This provides packages such as m2w64-toolchain which is a dependency of theano. It is best to add /msys2 as http://repo.anaconda.com/pkgs/msys2.
  • Constructor requires conda >=4.5.0

Devel

To build or update README.md at the root of the repo you'll need jinja2 installed

conda install jinja2

and then run make doc. Or invoke the script directly with python scripts/make_docs.py.

You can’t perform that action at this time.