Status
New Release Manager:
- Running RHEL4 builds
- RHEL5 will be activated when the RHEL5 boxes are reconfigured by SLAC Computing
- 64 bit builds could be activated at any time
- Windows builds were enabled yesterday - some wrinkles to fix
- Mac builds will begin once Qt is compiled
New Release Manager Web pages a week or more away [see minutes from this morning: https://confluence.slac.stanford.edu/display/SAS/Release+Manager+Web+Front+End+Discussion+October+2008
]. Current version is behind SLAC firewall and is available here:
http://glast-tomcat03.slac.stanford.edu:8080/releasemanager/releaseManager-NEW.jsp
Current version of SCons in use is 1.0.1
Science Tools
Builds using SCons are enabled and are being run through the new RM. The SConscript files do require maintenance. The hope is that once the new RM web pages are up and available, developers will be more likely to step in and tweak the SConscript files as necessary.
Joanne has asked that the ST externals.scons be updated to use ROOT 5.18c-gl1.
GlastRelease
Emmanuel has worked about SCons search for OBF libraries by temporarily setting an rpath (runtime path) option, so that builds will actually progress. This allows him to move forward as we work to work through a reorganization of OBF.
https://confluence.slac.stanford.edu/display/SAS/GlastRelease-scons+build+status
OBF
Three libraries have duplicate names.
Reorganization of OBF to conform to <externalName>/compiler/lib
In anticipation of our move to SCons and the reorganization of the externals to follow the previously mentioned convention, our CMT externals will be updated to follow the structure.
CHS
We use CHS/eventFile in the ldfReader package. At the very least CHS/eventFile must be updated to use SCons. After talking with Bryson, it is clear all of CHS will need to be updated in order to meet their requirement of running their regression testing through the ReleaseManager...and some of their existing scripts will have to be rewritten to work in a non-CMT world.
Bryson requests an checkout package-level example so that he may start porting the CHS checkout package to the SCons world. From Bryson:
We (FOS) use the CHS checkout package to build relocatable RPM's that we install in SLAC AFS space for our various software "platforms". We use glastpack.pl to extract a suitable source tree from offline CVS, and then build with CMT.
We rely on the RM HEAD and release build processing to perform the regression tests on the event-decoding software portions of CHS. However, to my knowledge there are no customers of the RM-created CHS build directory hierarchies in NFS.
Other Items
Tag Collector
Installer
Java installer with command line option
JobOptions file location transition
New Tagging Convention will be unleashed once tagging utilities are provided through GoGui and the tag collector
Note branch tags will have the form: xx-xx-xx-grx
Setting up the environment without CMT
Toby asks how will this work for Python?
Providing updated Documentation for the Workbook
Initial model will be to create pages (Confluence) that Chuck can point to. Ultimately the pages will be imported into the workbook when they have reached sufficient maturity. Further updates will be handled through the CVS checkout/update mechanism used by SciTools users.
Windows Discussion
http://confluence.slac.stanford.edu/display/SAS/SCons-Windows+Status+October+22%2C+2008
GoGui Demo for Joe the Plumber
GoGui is available on central linux. Outstanding issues Joanne highlighted on Monday:
1. Tagging Feature
Joanne would like to understand how most users tag. She (and I) primarily use rtag, but there are instances when the tag command is required. Joanne has located and understands the existing MRvcmt code. She should be able to translate it over to GoGui.
2. Windows
First step is to understand what SCons provides. Joanne is stuck trying to get SCons to create a VS project. It is expected that this will not provide all the required developer features we desire. The anticipated course of action will be to follow the model used for CMT, where we have separate code that builds the Visual Studio project files for us. Toby has some python code for this purpose and Tracy has previously worked with that code to force SCons to produce more useful project files.
3. Override directories
Need to modify the way we use SCons to make override directories possible. Some of Joanne's existing GoGui code assumes that this ability exists. The plan is to support one over-riding directory. Leon states he can live with that. That override directory may contain any number of packages. The fix will come in the SConstruct files, which while not pretty, will be invisible to most users.
http://confluence.slac.stanford.edu/display/SAS/GoGui+Status+and+Laundry+List
Where To From Here?
Demonstrating CMT and SCons equivalence.