Laserfiche WebLink
supporting configuration files) must be distributed to remote machines that are used by CRDSS <br />users. In such cases, a large data set will not need to be distributed. <br />Source code should also be encapsulated so that it can be "packaged," including documentation for <br />the program or routine. Keeping everything directly associated with a program with the program <br />assures that developers and users can understand how the program works. <br />Software that is stand-alone and can be used for multiple purposes should be placed in a "global" <br />xmgr <br />area so that it can be accessed outside of the CRDSS. For example, the program is public <br />domain program used for plotting graphs, and the program has no inherent ties to the CRDSS. <br />Consequently, this program should be placed on the system in a directory that can be accessed by all <br />users and developers, not only those who use the CRDSS. Placing generic utilities in a global area <br />also allows users and developers to quickly locate those programs. <br />RTi proposes that the following directory structure be used for the initial version of the CRDSS <br />(enhancements to this file structure will be made as source code and data are collected): <br />/crdss/README <br />doc/ <br />(general documentation) <br />modsim/*.f <br />*.c <br />include/*.h <br />doc/README <br />(man pages) <br />html/*.html <br />cu-model/ <br />system/ <br />(global configuration files) <br />libdmi/include/*.h <br />libgui/ <br />include/ <br />(may contain links to specific include files) <br />lib/libdmi.a <br />libgui.a <br />bin/ <br />(executables and scripts) <br />data/raw/ <br />processed/ <br />/usr/local/bin/ <br />xmgr/ <br />xv/ <br />/usr/man/manl/*.l <br />(man pages) <br />/usr/lib/X11/app-defaults <br />(application defaults) <br />Directories in the file structure are followed by a /. Note that this file structure is displayed as <br />absolute as a convenience to users and developers. However, UNIX offers "symbolic links," which <br />allow a file or directory to be linked to another location. For example, the entire CRDSS file <br />structure or parts of it may be installed under the directory . The symbolic link <br />/disk1/crdss <br />from to allows users to access files using a directory structure that is easy <br />/crdss /disk1/crdss <br />2 <br />A275 05.10.94 1.05-23 Malers <br />