Am Freitag, 14.03.03 um 21:13 Uhr schrieb David R. Morrison:
[...]
How exactly could this be done? Considering that scripts can include arbitrary other scripts? Also, the "source" statement could be commented out etc.case yes) check if "source %p/sw/init.csh" is already in the .tcshrc
What I want to say is: tools that manipulate shell scripts (or other textual config files) always have a big potential of messing up if not designed very carefully. The only way to get them always right usually is to fully parse the file in question, but that's not really feasible for shell scripts, I fear... I do not want to make this idea bad, I just want to stress that it's vital such a tool is designed and tested with this in mind. In particular, a suite of test cases should be defined and then any release of that tool run on that test suite. At least the default actions should never mess up the system.
Max
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel