(Toby) Since SCons development has to be done in parallel with running the old system, presumably we don't want to make any changes to requirements files just to aid this development. We need a place to put the SConstruct file. (Jim) Normal practice is to put it in the source directory. In fact SCons expects all source (implementation; that is, .cxx) files to be in a single directory [correction: it's only SConstruct files generated with Jim's automatic translator that has this requirement, not SCons]. Also objects are created in the source directory. [This makes it sound like it's not possible to build—and keep—binaries for different architectures or compiler settings, from the same source, but SCons has a concept of Install which could perhaps take care of this; see the User Guide. Ed.]
(Heather) We need to talk to Riccardo to be sure the new scheme, however it develops, will be compatible with MRStudio without a major overhaul.
The other problems noted with the Installer are ftp-glast problems. One such problem was Richard's CLHEP problem today. It seems to hang after only downloading a few hundred KB. I've verified this is an ftp problem. Richard sent an email to unix-admin asking for help. [Contribution from Richard notes that he also had a Mac-specific problem: gui apps on a Mac don't use $PATH so gtar wasn't found.]
It would be nice if the Installer could report more user friendly error messages when trouble occurs, and perform checks to be sure what is installed is correct. Testing for completeness and correctness, however, is not a simple task. As the Installer is an important utility and will likely gain importance to the user community as launch approaches, we need to insure it works consistently and correctly. (Navid) The Installer could move to use HTTPS instead. (Richard) If so it should probably be through a GLAST web server, rather than SLAC's web server, as we have caused SLAC's web server fits in the past.
previous | minutes index | next |