X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "David Christensen" To: References: Subject: RE: Wish Setup would accept my Perl Date: Thu, 6 Dec 2007 22:43:55 -0800 Message-ID: <008f01c8389c$8a7ed280$0a00a8c0@a64x23800p> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Michael Kairys wrote: > I see that quite a discussion has evolved since last I checked this > thread. Likewise. I've gone round and round on the issues of command.exe, Windows Explorer, Cygwin, and Perl. Perl libraries and the various maintenance tools add yet another dimension of complexity. Going through the various combinations and permutations was very confusing and led to much frustration and wasted effort. My solution was to limit myself to Cygwin, Cygwin Perl, Cygwin Perl libraries, and Perl libraries built from source (using Cygwin tools). If I want to light off a Perl script from Windows land, I write a batch file. This approach is the easiest for me to understand, and works reliably. HTH, David -- 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/