CASA Software Engineering Project: Evaluate Cross Platform Package Managers

The list of CASA supported OSs has grown from 2 (RHEL 4.x and one version of OS X) to 7, and there is ongoing pressure to increase support. CASA has been trying to distribute native packages for both 3rd party development tools and published CASA packages. At this time, CASA is not meeting OS support requirements, and does not look like it can within available resources.

Evaluate cross platform package managers to see if any help reduce the work of delivering CASA 3rd party packages to developers and CASA packages to users enough to offset the costs of adoption.

Status: See CAS-5685.


  • CASA Developers



  1. Collect requirements.
  2. Collect candidates.
  3. Eliminate candidates as quickly as possible.
  4. For each of the top three remaining candidates.
    1. Try with trivial example
    2. Try with non-trivial example
  5. Evaluate


  1. Requirements used to evaluate candidates.
  2. List of all candidates evaluated.
    1. For each reject, give reason.
  3. Report comparing top three candidates, with recommendation.
  4. Admin instructions for setting up candidate for use by users.
  5. User instructions for using candidate to install CASA 3rd party packages for developers.
  6. User instructions for using candidate to install CASA packages for users.


Candidate cross platform package managers must meet these requirements:

  1. Co-exist with native platform package managers for all CASA supported OSs.
  2. Allow us to override platform packages without breaking other software on that platform.
  3. Allow us to install several consistent sets of CASA 3rd party packages and CASA packages at the same time without interfering with each other. For example, to support old and new 3rd party packages while transitioning between versions.
  4. Not require complex configuration by users.
  5. Allow CASA to deliver binary packages.
  6. Minimize the number of platforms we must build on before publishing packages.
  7. Allow users to install binary packages where they like (and have write permission), without rebuilding.
  8. Allow users to setup a developer environment easily.
  9. Must not cause CASA to run more slowly.


(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.)


(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.)


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

-- ScottRankin - 2013-09-30
Topic revision: r2 - 2013-09-30, ScottRankin
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback