Yet another way this can go bad (that I hadn't thought of) is described in:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06499.html In this case, the .login explicitly sets the path, overwriting what was already done in .tcshrc or .cshrc. So, it's going to be difficult to get this set up in a way that works in every situation. However, I still contend that even automating our current instructions would be an improvement. (After all, anyone who follows the current instructions in a case that they are incompatible with a pre-existing setup will be in exactly the same situation.) -- Dave ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
