Hall D Package Manager
This is a set of scripts with a unified user interface for managing Hall-D software. It allows one to build and update Hall-D software from a single directory, and makes it easy to view and modify current package versions. The main idea is to configure builds with a series of simple text files, separating the process of scripting from configuration, and providing templates for future builds. The configuration text files are meant to be general enough so that the user will never need to modify any of the source scripts. Secondly, an effort is made to minimize the number of lines a user will need to modify in order to (re)configure a build; the scripts recognize certain variables, such as [VER] for version number to make this possible. Example templates are provided; most of these are designed for use on the JLab CentOS 6.5 iFarm, but can easily be modified for general use. Hall D Package Manager (hdpm) is located at the GitHub along with a thorough README.
git clone https://github.com/JeffersonLab/hdpm
If on 64-bit Linux, change to hdpm directory and source the appropriate setup script. This is for setting up the package manager, not the builds, and needs to be done each time a new shell is started.
If on Mac OS X, manually download the Julia dmg, put executable in PATH, change to hdpm directory, and make an alias for running src/hdpm.jl:
export JULIA_DIR=/Applications/Julia-[VER].app/Contents/Resources/julia export PATH=$JULIA_DIR/bin:$PATH alias hdpm='julia src/hdpm.jl'
For help, just type 'hdpm' or 'hdpm help'.
Select an example build template; "all", "deps", "Sp15", or "F14".
hdpm select <template id>
Show the current build settings. Note that these arguments are optional. Column names: "name", "version", "url", "path", "nthreads", and "tobuild".
hdpm show [column name] [column spacing]
Customize build templates by editing/copying the text files in the "template"s directory (which start off as copies of "example-templates"). The current build settings are stored in the "settings" directory; these should be directly modified when the user wants to try out new settings. These can then be copied over into the "templates" directory with an appropriate tag for future use after being tested.
Checkout, clone, or download selected packages.
Build selected packages.
Checkout/clone/download and build selected packages. Argument is optional.
hdpm install [template id]
Update selected packages.
Do a clean build of selected packages.
Show usage and description for command.
hdpm help <command>