Visit CASA.md for instructions on installing CASA in an Anaconda Python environment. Except, those instructions are old and out of date! Just use conda-forge and Pixi.
This repository contains the tools I use to build various packages for the
Conda package manager. Builds are provided on 64-bit Linux and OS X. My
packages are layered on top of those provided by the conda-forge project, so
you must add conda-forge as a channel in your Conda configuration!
I upload built packages to my personal anaconda.org channel. You can configure your [Anaconda] installation to fetch packages from it with:
conda config --add channels pkgw-forge
To directly install the package aoflagger (for example) without altering your
configuration, use:
conda install -c pkgw-forge aoflagger
As part of this work I’ve also developed a prebuilt Docker image that can be
used to repeatably build binary linux-64 packages. For OS X, I use Vagrant
to make osx-64 packages repeatably. My notes for developers may be
valuable if you’re interesting in making Conda packages containing compiled
code for Linux and/or Mac OS X machines.
There are two main components to how I build my Conda packages. First, I have set up a Docker environment that allows me to build packages repeatably inside a stable, containerized Linux environment. Then, I’ve written the Conda recipes that actually define the packages that I build. I’ve written up notes on how the system works if you might be interested in doing similar things.
OK, there are three components — I use Vagrant to generate and drive a repeatable, headless build environment for the OS X package builds.
The Conda recipes are licensed under a 3-clause BSD license, for compatibility with the main conda-recipes repository. See the file LICENSE.txt for the details. Other files are licensed under the MIT License.
Copyright Peter Williams
This file is free documentation; the copyright holder gives unlimited permission to copy, distribute, and modify it.