CASA Software Engineering Project: Build Casa 3rd Party Packages Using MacPorts

As discussed in the 2013 CASA Developer's meeting, build all CASA 3rd party packages on OS X using MacPorts. Distribute the results to CASA developers so that they do not have to build CASA 3rd party packages for themselves.

Status: See CAS-5903.

---

---

Team

• ScottRankin

Customers

• CASA Developers

Collaborators

• DarrellSchiebel

Plan

1. Starting from a procedure provided by Darrell in e-mail, build CASA 3rd party packages on OS X 10.7, 10.8, and 10.9 by any means necessary.
   1. Build 3rd party packages in /opt/local on OS X after a clean OS and Xcode install.
   2. Copy built 3rd party packages to another OS X system with the same OS version. Do not clean the target system before use.
   3. Build CASA, record issues, fix issues, iterate.
2. Distribute built 3rd party packages to CASA developers who can use them for testing.
   • Initial results will not be usable by NRAO CASA developers without removing NRAO Managed Software.
3. Update CASA OS X package build process to use built 3rd party packages.
4. Update process to install MacPorts and built software in /opt/casa/3rdParty/N, where N is a version number for the 3rd party package build.
   • This is to avoid breaking other uses of MacPorts, including NRAO Managed Software.

Requirements

Deliverables

1. Built CASA 3rd party packages.
2. Instructions for installing and using built 3rd party packages.
3. Instructions for building CASA 3rd party packages from source for those who can not use the built 3rd party packages.

Technical

1. Final results must not break.
   1. NRAO Managed Software.
   2. Other users of MacPorts default installations.

Design

(Note: replace this note with a one paragraph summary of the design for this project, a short bullet list of design details, or link(s) other pages documenting the design for this project.)

Implementation

(Note: replace this note with a one paragraph summary of the implementation for this project, a short bullet list of implementation details, or link(s) other pages documenting the implementation for this project. Often, this will be a bullet list including the location for any source code in change control and any user accounts or computers required by this project.)

Tasks

Project tasks are tracked with Jira sub-tasks under this project's master task. See CAS-5903.

-- ScottRankin - 2013-12-11