Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-envelope-info: Message-Id: <5.2.1.1.2.20030509162745.067470e8@pop.sonic.net> X-Sender: rschulz AT pop DOT sonic DOT net Date: Fri, 09 May 2003 16:34:47 -0700 To: cygwin-xfree AT cygwin DOT com From: Randall R Schulz Subject: Re: Wanted X, got Perl - operator error or prequisiste Cc: cygwin AT cygwin DOT com In-Reply-To: <200359191813.562828@mopxp> References: <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030508222724 DOT 02a51730 AT pop DOT sonic DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Matthew, At 16:18 2003-05-09, Matthew O. Persico wrote: >On Thu, 08 May 2003 22:32:46 -0700, Randall R Schulz wrote: > >Matthew, > > > >At 22:12 2003-05-08, Matthew O. Persico wrote: > >>... > >> > >>>The *.pl scripts in XFree86 mean nothing --- they are not needed > >>>for the normal operation of the X Server. > >> > >>Then I'll just whack 'em. > > > >Why? Why muck with files installed by a package you're using? Does > >there mere presence cause a problem? If so, how and why? They'll just > >come back when you update that package as the next release becomes > >available. > >Because when I want to run Perl, I want ActiveState Perl 5.8.0 >installed in C:opt\asperl and I don't want any chance of that not >happening. This is the most mindless way of getting that to happen. >And after supporting three (yes THREE) versions of Perl on multiple >machines in different locations at work (not I didn't set it up, I >just inherited it and I'm working on fixing it ), the last thing I >need is to cause myself ANY problems at home. This does not follow. Perl scripts installed along with one of the X packages aren't going to cause the wrong Perl to get executed. How could they? > :-) > >Oh, and when I said "whack", I really meant "uninstall using setup.exe". Setup.exe doesn't allow you to uninstall individual files within a package, nor should it. >-- >Matthew O. Persico I have ActiveState Perl and Cygwin Perl installed, and there's no conflict. The PATH variable resolves them just fine. When I run Perl scripts within Cygwin, the Cygwin Perl interpreter is used. When I run them outside Cygwin (say, as CGI scripts for Windows Apache), I get ActiveState Perl. Software running on digital computers (that are not malfunctioning) is deterministic, after all. Randall Schulz -- 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/