|
From: Harlan S. <Har...@pf...> - 2002-10-24 06:17:16
|
So I'm trying to convert the users of a large project to modules (config management of the build toolchain). There are most of the usual shells involved. There are people who use wildly different RC files for each of these shells. The manager does not want to ask people to change their RC files. He suggested that since we do require people to source a $SHELL-specific file already, we simply add the module init code to those files and (hopefully) transparently solve the "cutover" problem. The problem I'm having is that while our additions give people the right environment for building the code, people now want to use modules to make sure they get, for example, the same version of emacs on all platforms. This is, of course, easy with modules. The tricky part is that their normal RC files don't know *anything* about modules, and we would prefer to keep it that way. I was hoping I could simply give these folks a ~/.modules file that would be the place where they put their customizations. The good news is that the "module init*" commands see the ~?.modules file and DTRT there. The bad news is that apparently this file is not processed! Any thoughts on how I can solve this problem? H |
