<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div dir="ltr">
<div>
<div>Folks,<br>
<br>
Over the past few months I have been transitioning the public
builds on the CUE to conform with the version management
system which I have described at the offline meetings. This
has changed the directory structure under
/group/halld/Softwarae/builds . The new scheme has a separate
GLUEX_TOP for each platform we support at the lab. They are
named after the BMS_OSNAME variable and have names like
Linux_CentOS6-x86_64-gcc4.4.7 . The individual package
directories, e. g., jana, sim-recon, and hdds, are stored
under GLUEX_TOP with mulitiple versions of the packages stored
under the appropriate directory, for example, sim-recon-1.0.0,
sim-recon-1.3.0, etc. Environment set-up using the new scheme
is supported by the gluex_env_jlab.(c)sh scripts in
/group/halld/Software/scripts/build_scripts . That script
serves as an example if the default versions are not what you
want.<br>
<br>
</div>
The old scheme had the package directories (jana, sim-recon,
etc.) directly under /group/halld/Software/builds . All builds
using those directories are pretty old and probably not suitable
for general use now, but have been maintained for backward
compatibility with older projects.<br>
<br>
</div>
Lately I have realized that the old-scheme directories are causing
confusion for people browsing the Software/builds directory. To
avoid this, I am planning to move these directories out of
Software/builds to a subdirectory, Software/builds/legacy . This
will require old projects to adjust their environment set-up
scripts.<br>
<div>
<div><br>
</div>
<div>I plan to do this at the end of the day this Friday, July
10, unless I hear objections.<br>
<br>
</div>
<div> -- Mark<br>
<br>
<div>-- <br>
<div class="gmail_signature">Mark M. Ito<br>
<a href="mailto:markito3@gmail.com" target="_blank">markito3@gmail.com</a><br>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>