rusty@groan.Berkeley.EDU (Rusty Wright) (06/05/91)
Well, not really, but it needs improvement; I used that subject line to get your attention. The point of this message is that since CAP 6.0 is using a Configure shell script it should be able to prompt you for the names of the directories where it gets installed; that is, the defines for capdestdir, capsrvrdestdir, and libdestdir are hard-wired in Configure and they shouldn't be. I have to install CAP on a fileserver that supports binaries for 4 different machines and it is a pain in the butt to have to edit the m4.setup file every time after I run Configure. Of less importance to me, but possibly useful, would be to have a file similar to m4.features but for local mods that are specific to your os/arch. For example, m4.local_bsd, m4.local_ultrix12, m4.local_ultrix20, m4.local_ultrix40, m4.local_hpux, etc. When m4.setup is run it would suck in the appropriate m4.local_os file.