I'd keep the cygwin stuff since it's not going to harm anything. It's not much and it's pretty standard issue. It's a single block that massages the variables once and it's done so I don't think it's that much clutter.
But you do have a point about us having different installers for windoz verses *nix. Regards, Alex On 3/28/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Thanks Chris, I can shove them back in if need be. I asked Alex just now...If we have *NIX installers and Windows installers that let the user run ApacheDS using .bat files, does the user still need Cygwin? WDYT? Thanks, - Ole Chris Custine wrote: > The path vars will definitely not work in Cygwin without those > conversions. Its ugly, but lots of projects use the same type of > conversions to maintain Cygwin compatibility. > > Chris > > On 3/27/07, *Alex Karasulu* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Yeah this is for windows but if you want the script to work in the > cygwin environment you're going to need this stuff. > > Really if you want to chop this stuff out I recommend checking > that it still works in cygwin before doing so. Do you have > a cygwin environment? > > Alex > > > On 3/21/07, *Ole Ersoy* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > wrote: > > Howdy, > > In the start/stop script there's this Cygwin stuff: > > # For Cygwin, ensure paths are in UNIX format before anything > is touched > if $cygwin ; then > [ -n "$APACHEDS_HOME" ] && > APACHEDS_HOME=`cygpath --unix "$APACHEDS_HOME"` > [ -n "$APACHEDS_HOME_LOCAL" ] && > APACHEDS_HOME_LOCAL=`cygpath --unix "$APACHEDS_HOME_LOCAL"` > [ -n "$JAVA_HOME" ] && > JAVA_HOME=`cygpath --unix "$JAVA_HOME"` > [ -n "$CLASSPATH" ] && > CLASSPATH=`cygpath --path --unix "$CLASSPATH"` > fi > > nuke? > > I think cygwin stuff is just for running on windows right? > > Thanks, > - Ole > > >
