On 03/05/2013, at 9:31 AM, Adam Neather wrote: > Cheers much. For some reason, the setenv command worked this time; > where as before it didn't. The ~/.tcshrc file has been created (as > both of the open -e commands listed above reported no such file) and > port is working correctly. Huzzah!
Something is mystifying me about this discussion. Am I missing something or has something in MacPorts changed? As I understand Unix-like systems, there are three scripts that can operate when you are logging in: .login, .profile and .<shellname>rc. Also, that there is a convention that these scripts should be compatible with the Bourne Shell, or nowadays "bash", the Bourne-again Shell. When I started with MacPorts about two years ago, I was surprised to find that it put its login-time commands into .profile and there they still are. In Linux and Unix I would have put such commands in .bashrc or, back in the day, .kshrc. I have followed along with what I took to be the Apple convention and put lots of other stuff into .profile rather than .bashrc (e.g. several command aliases). I got the impression, too, that .bashrc does not run when you start an Apple Terminal window, but only when you manually start a new "bash" shell. Am I doing things wrong? Maybe I missed something in the flurry of setting up a new system and MacPorts two years ago. Cheers, Ian W. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
