May I suggest that we break out the Cygwin case into a separate script, so we don't need to worry what effect it has between the different platforms.
For instance; merlin.bat = Windows merlin.sh = Unix/Linux merlin.cyg = CygWin
I would feel more comfortable with this SoC... ;o)
Putting on my user hat for a moment, most people just want to type one command regardless of the platform. In this case they just want to deal with "merlin":
> merlin
Even the ".sh" extension is not common for the base command--though it is common for called scripts. For example if there was the following:
merlin merlin.bat merlin-cygwin.sh merlin-unix.sh merlin-darwin.sh
Then all would be well. The user can still get the ball rolling with the same command on both Windows and Unix (and derivative OS), while the script writer can dole out the environment specific stuff to the .sh scripts.
That would give what you want and what the user wants. Most folks believe it is easier to maintain one script file so that is why things like Merlin, Maven, and ANT have everything in one file.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
