Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • 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 

Wiki MarkupNew 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 .  Current version is behind SLAC firewall and is available here:

http://glast-tomcat03.slac.stanford.edu:8080/releasemanager/releaseManager-NEW.jsp

...

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.
 

CHS Update 2008-10-24 by Bryson
I've got the CHS package mostly building under SCons. What's missing are three modules from the top level of CVS that are used, I think, by ConfigSystem and nothing else, and don't yet have SConscript files:

  • LATC_vrfy
  • MOOT
  • fswDecipher

Of these, LATC_vrfy looks moderately complicated to convert, since it reaches out heavily into FSW's production CMX instance to find things like the register descriptions.

...