activestate perl on cygwin

I understand the trouble with using Activestate perl on cygwin is the path conversion problem. Searching online I found the following wrapper script useful for most perl commands: #! /bin/sh # This is necessary to make perl work with cygwin. Cygwin passes # "cygwin style"

RE: activestate perl on cygwin

I don't actually install through cygwin, but use the ppm installer from Activestate. I still need to know how to solve the issue that occurs with the command I mentioned in my original post. Using the version of perl installed with cygwin is not really an option since I already have scripts written

RE: activestate perl on cygwin

Win32::Mechanize Win32::OLE Win32::GuiTest Win32::Process -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yitzchak Scott-Thoennes Sent: Tuesday, January 09, 2007 10:58 PM To: cygwin@cygwin.com Subject: Re: activestate perl on cygwin Kevin T Cella

RE: activestate perl on cygwin

Sent: Wednesday, January 10, 2007 9:06 AM To: Kevin T Cella Cc: cygwin@cygwin.com Subject: Re: activestate perl on cygwin On Mon, 8 Jan 2007, Kevin T Cella wrote: > I understand the trouble with using Activestate perl on cygwin is the > path conversion problem. Searching online I found th

RE: activestate perl on cygwin

> . Thanks. Seeing as I do not know how to configure this, I cannot oblige. >> Offer an alternative. As I mentioned in my original post, I got this >> script online. In using it I found it was not sufficient, I started this >> thread in the hopes that

RE: activestate perl on cygwin

> But it is a bad idea to use ActiveState under Cygwin. Would you prefer > if we lied to you? No, I'd prefer you answer my question. I can't use Activestate perl on cygwin by not using Activestate perl on cygwin. Do you see the contradiction? >> My scripts are written to make my life on Windows

RE: activestate perl on cygwin

> Actually, being technical about this and looking at your OP there is no > question there at all! Search for it. Look for a question mark. There is > none. There is merely the sentence "Please advise" and that's what you got! Congratulations! I was wondering when someone would point that out; a

RE: activestate perl on cygwin

> [snip] you only need the wrapper script to transform the script name from > POSIX path style to Win32 style, and only if it's in the #! (shebang) > line of a perl script. That was what my wrapper script was designed to do > (as shown by the example usage). You do NOT need a wrapper to run the >

RE: activestate perl on cygwin

> [snip] but the point of this little story is that you > are short sighted if you believe that the only platform you'll > encounter and thus need to deal with is Windows... I agree completely. This is for personal use. > As has been pointed out to you already there is Win32 modules for > Cygwin'

RE: activestate perl on cygwin

> That particular case is handled by the wrapper script I posted. Note > that > you *don't* need to use the wrapper script to invoke perl on the > command > line -- only in the #! (shebang) line of your script file. I know. Thanks. I was just trying to oblige the request from Mr. DeFaria. -- Un

RE: activestate perl on cygwin

> Well, I run perl scripts on cygwin with no problem. Did not do anything > special, > except > make sure NOT to install perl when installing cygwin(and making sure > the activestate perl is in the path) I tried this, but it still does not work. -- Unsubscribe info: http://cygwin.com/ml/#u

RE: activestate perl on cygwin

> What does that matter? It's still short sited. Yes, I don't disagree. Personally I do not care. I will deal with having to port something when it happens. > And what does #! look like? #! /usr/bin/perl > what does ls portion after #! in your script return? Before the conversion using cygpath

RE: activestate perl on cygwin

> > > And what does #! look like? > > #! /usr/bin/perl > Is there something that the space after the "!" and before the "/" buys > you? Readability. It is simply a question of style. I prefer the space. Has it come to that? > So your specifically saying by your shebang line - execute Cygwin's >

RE: activestate perl on cygwin

> I simply asked a question. You provided an answer. > Whose undies are in a bunch here? As did I. Sorry I misinterpreted your tone. > Wouldn't it be much more > "stylistic" and clear to simply point directly at the Perl you insist > on > using? Or did you really mean you are putting /usr/bin/pe