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> <009701c7357f$4b05f9b0$e111ed10$@rr.com> <eo5fer$f6e$1 AT sea DOT gmane DOT org> <00af01c735f2$43713980$ca53ac80$@rr.com> <eo77ee$bqv$1 AT sea DOT gmane DOT org> <00d701c73646$7d628e10$7827aa30$@rr.com> <eo83fl$87k$1 AT sea DOT gmane DOT org> <00e301c736a6$a66de740$f349b5c0$@rr.com> <eo9co7$1gq$1 AT sea DOT gmane DOT org>
In-Reply-To:	<eo9co7$1gq$1@sea.gmane.org>
Subject:	RE: activestate perl on cygwin
Date:	Sat, 13 Jan 2007 00:39:29 -0500
Message-ID:	<00e801c736d5$32b9a670$982cf350$@rr.com>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 12.0
x-cr-hashedpuzzle:	amY= AEmV AFE9 AkpW A9RS CNQ+ Cv5Y C8ZU DmsG E56Z GHtT HBjA H0Fc JgV/ Jnmr JriU;1;YwB5AGcAdwBpAG4AQABjAHkAZwB3AGkAbgAuAGMAbwBtAA==;Sosha1_v1;7;{A95525EB-DC81-4EC4-8B67-9987AE712A66};awBjAGUAbABsAGEAQABuAHkAYwBhAHAALgByAHIALgBjAG8AbQA=;Sat, 13 Jan 2007 05:39:19 GMT;UgBFADoAIABhAGMAdABpAHYAZQBzAHQAYQB0AGUAIABwAGUAcgBsACAAbwBuACAAYwB5AGcAdwBpAG4A
x-cr-puzzleid:	{A95525EB-DC81-4EC4-8B67-9987AE712A66}
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

> > >  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
> perl.

As I state later, I use a symlink so I am infact executing Activestate perl.
Seriously, are you trying to attack me or understand the problem? I am
trying to be nice, I already apologized for my behavior earlier.

> >> what does ls portion after #! in your script return?
> > Before the conversion using cygpath, it returns the same as in the
> > error: /home/kcella/bin/myscript.pl
> So then you are saying that you have no /usr/bin/perl? Is so then why
> do
> you put "#! /usr/bin/perl" in your script at all?

I think I misunderstood the question. I had taken it to mean had I
executed an ls on the incoming argument to my wrapper script (ie: the
script filename), what would be the output. Now I see what you were
trying to get at was if the interpreter referenced by the #! line exists
on my system. As I state later, I use a symlink:

$ ls -l /usr/bin/perl
lrwxrwxrwx 1 kcella None 20 Jan 13 00:19 /usr/bin/perl ->
/c/Perl/bin/perl.exe

> So now you are saying that you have no problem?!?

Keep reading...

> > The example I gave is for when I have no wrapper script and just
> > create a symlink in /usr/bin/perl that points to
> /c/Perl/bin/perl.exe.
> Huh? There is no /c/... although I've heard of a way to do that I've
> also heard that it's not supported. Futher, why would you want to
> symlink /usr/bin/perl -> /c/Perl/bin/perl.exe?!? Or, since you insist
> on
> using ActiveState, then why not specifically specify something like
> #!C:/Perl/bin/perl.exe or something like that?

Again, it is just a question of style. I have done it both ways, I
prefer using linux style pahts. I mount c: to /c because it is
much faster to type than /cygdrive/c/ and it makes more sense from
a readability standpoint.
 
> > The root cause of the example is the reason for the initial post. The
> > wrapper script was the solution I happened to choose to get around
> the
> > path problem, but quickly found out that it does not work properly
> > with: perl -e 'print join "\n", @INC, "\n";'
> >> Oh and what is PATH set to?
> >
> /home/kcella/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Perl/bi
> n/:/c
> > /WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem
> You could probably also simply use #!perl since C:/Perl/bin is in your
> path...

Another question of style. Although for me it is more habitual
than stylistic. Your questions are very subjective with an insulting tone.
I'm sorry if I have offended you in some way. Do you at least understand
Why the cygwin style paths are causing an issue? And what it is I am trying
to accomplish?



--
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/

- Raw text -