On Jun 27, 2004, at 8:07 PM, Martin Costabel wrote:
1. The users that complain about the error message now will complain about the warning as well. You would have to include into the warning an explanation of how to purge the startup script so that the warning goes away. A reasonably-sized understandable warning is probably more difficult to write than a "remove-fink" script that does this purging automatically.

2. Worse than a ~/.cshrc that breaks is a ~/.cshrc that produces text output. It will break configure scripts in hard-to-debug ways, for example. There would have to be some non-trivial logic to make sure the warning is only written when the output goes to a terminal.

So why not just leave it like this?

[ -f /sw/bin/init.sh ] && . /sw/bin/init.sh  # http://url.to/explanation

If it's not there, we simply fail silently. The vast majority of users will never notice it, and the ones that do can follow the URL.

Dave

Attachment: PGP.sig
Description: This is a digitally signed message part



Reply via email to