Ok np you got me screaming uncle :). Let's remove it then if others don't have an issue ... and if need be we can revert and add it.
Alex On 3/28/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Hmmm The only thing I think is weird about it, is that it sort of implies that someone could or might want to run it in a Cygwin environment. Which sort of implies that we've tested it in a Cygwin environment, and support that type of configuration. Which I think if were going to keep it, we should actually do. However this is more work, and given that we have installers for both OSs,.... So I'm thinking 99.9% of users will grab either the *nix installer or the windoz installer. Then .1% will grab the *nix and perhaps try to run in a Cygwin environment. Then they may ask for support, and since we have that in there, we should probably have answers with respect to how we've tested it. And then we would probably ask why don't you just install it straight up on windoz? And half may say Ohhh - There's a windoz installer? I think we should leave it out, and then if there's a lot of support inquiries about running in Cygwin, put it back and have the supportees help us out with validating the configuration.... And if anyone really really feels strongly about it, then I'll just shove it back in :-) Cheers, - Ole Alex Karasulu wrote: > 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] > <mailto:[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]> > > <mailto:[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]> > > <mailto:[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 > > > > > > > >
