X-Spam-Check-By: sourceware.org
From: "Kevin T Cella" <kcella AT nycap DOT rr DOT com>
To: <cygwin AT cygwin DOT com>
References: <000301c733a2$28c29db0$7a47d910$@rr.com> <Pine DOT GSO DOT 4 DOT 63 DOT 0701100857580 DOT 6616 AT access1 DOT cims DOT nyu DOT edu> <006901c73528$574b11d0$05e13570$@rr.com> <eo4fat$7v0$1 AT sea DOT gmane DOT org>
In-Reply-To: <eo4fat$7v0$1@sea.gmane.org>
Subject: RE: activestate perl on cygwin
Date: Thu, 11 Jan 2007 07:52:03 -0500
Message-ID: <009701c7357f$4b05f9b0$e111ed10$@rr.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: en-us
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> 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 easier, so that 
>> means using Windows specific code to automate common tasks.
> But you really don't need to do such things in a "Windows specific" way! 
> I used to run my whole domain under Cygwin. Apache for my web server, 
> exim for a mail server, Cygwin's own inetutils for ftp, ssh, etc. 
> Everything ran fine albeit a bit slower due to the fact that Cygwin is 
> an emulation environment.

Seeing as how you don't know what common tasks I am trying to automate,
I don't see how you can presume to know the scripts do not have to be
written in a Windows specific way. Suppose your theory is that any script
written for Windows can be written to work with Linux. As I stated earlier,
I do not wish to port my existing scripts to cygwin.

> And if the real, long term, more portable solution is to use a Cygwin 
> based, thus more normal Perl...

I'm asking for the short term solution.

> Answers were provided to you. Apparently they don't tickle your fancy. 
> People have commented on that wrapper script that you posted. I still 
> don't see what your problem is. If your Perl script expects 
> C:\mydir\foo.dat then give it C:\mydir\foo.dat. Of course you'll need to 
> do that under a cmd shell or, for Cygwin's bash shell you'll need to 
> double the backslashes (C:\\mydir\\foo.dat) or use forward slashes 
> (C:/mydir/foo.dat). If you insist on giving your Perl script 
> /cygdrive/c/mydir/foo.dat then perhaps your Perl script should expect 
> that and translate it. A quick Perl subroutine to do that shouldn't be 
> that hard to code.

Other posts have indicated how this is not possible. Executing a script
That appears in my $PATH will automatically expand using cygwin style
pathing. Answers were provided, but not to my original question. I still
have no way to execute the command below and a regular script on cygwin
using Activestate.

perl -e 'print join "\n", @INC, "\n";'



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/