MDSplus packages are available for a number of computing platforms. Additional platforms can usually be supported by downloading the MDSplus sources and building directly on the computer where you want to run MDSplus.
MDSplus for Redhat Linux Distributions
Redhat Linux uses the Redhat Package Manager and the installation kits are stored as rpm files. Redhat systems also provide package distribution and updates using yum repositories. Here is a link to the Latest RPM's and Yum repositories to find the yum repository setup and the latest rpm downloads.
Microsoft Windows Distributions
Setup programs are available for the Microsoft Windows platform. Both 64-bit and 32-bit kits are available. The 64-bit kits contain both 64-bit and 32-bit libraries and programs so there is no need to install both a 64-bit kit and a 32-bit kit on a 64-bit system. Here is a link to the Latest Windows Distributions.
MDSplus for Ubuntu
Ubuntu uses a different packaging for their software installation kits. Here is a link to the Latest Ubuntu Packages to find MDSplus packages for these systems.
MDSplus for Solaris Distributions
MDSplus Package Depots have been created for Solaris systems. Click on Solaris Distributions to find directions for installing and configuring MDSplus on Solaris systems.
MDSplus for Mac OS X
Macintosh packages have been been built for some macintosh platforms. Click on Latest Macintosh Distributions to find information on installing MDSplus on Machintosh platforms.
MDSplus Source Tarballs
The following table contains links to the MDSplus source tar files used when creating the various distributions.
The latest MDSplus python modules are included in various installation kits and are also available for download on this page.
MDSplus Build System
MDSplus distributions are now being built using a build system called Hudson. On a regular basis (currently nightly), MDSplus installation kits are being built for several computing platforms. Kits for each of three release levels; stable, beta and alpha are updated as needed. These three release levels correspond to the stable branch, beta branch and HEAD of the MDSplus cvs repository. The builds are run on VMware virtual machines, one for each computing platform supported. You can view the MDSplus build system and see logfiles of various builds as well as the CVS changes made impacting the various releases. When the build system detects a CVS change in the corresponding CVS branch a new release of the affected kit will be built and the last field of the kit version will be incremented. Once a particular branch has been tested and is relatively stable, that branch will be promoted to the next release level (i.e. alpha->beta or beta->stable). When a branch is promoted, both the source branch and the destination branch will receive new version values (first and second fields of the kit version). For example, if a kit has a version of 4.1.2, the 4 is the major version number, the 1 is the minor version number, and the 2 is the release number. When major functional changes occur then the major version number will be incremented and the minor version and release numbers will be set to 0. When minor functional changes occur the minor release number is incremented and the release number is set to 0. When minor bug fixes are made to any of the branches, the release number will be incremented. This versioning is similar to the numbering used for most linux distributions.