...
So far we know of one detail in the way override directories are treated which doesn't have quite the right behavior for the ASP situation, but there is a simple way to extend the existing behavior to suit the new situation as well as the old. There may be other small glitches; we don't expect anything major.
What is where
The files comprising the SCons machinery are of different types and reside in different places:
- package-specific For each package there must be a file called SConscript. For packages building libraries there must also be a file _pkgName_Lib.py. Both are in the package root directory
- global, container-specific The file package.scons and the file externals.scons, kept in the top-level directory of the container
- global, generic These files are identical for all containers. Only a single copy is kept in CVS (under SConsFiles). This category includes the files SConstruct, processExternals.scons, allExternals.scons and several tools in site_scons/site_tools
Up till now, in the case where there is an override directory, all the global files come from the base, but if the override directory is container-like it might need its own copy of the category 2 files. ASP needs its own package.scons (which should override the ScienceTools one) but, as currently constituted, does not need its own externals.scons.