On 11/5/07, Michael Kairys <[EMAIL PROTECTED]> wrote: > I've been using ActiveState Perl and Cygwin together for years and have only > one complaint: Setup keeps hassling me about dependencies and I have to make > sure always to uncheck Perl in the setu list (and again in the dependency > check) or I end up with two Perl installations, which I don't want. > > I wish Setup could recognize that I already have a Perl installation... >
The answer is "Don't do that". Perl on cygwin and ActiveState Perl are completely different things. You've been using them together for years [without problems], [except for this one big problem]. ActiveState Perl is a Windows app and should only be accessed through Windows, such as the cmd.exe window or by using the .pl file extension. If you think the cmd.exe window sucks, try console2 on sourceforge. It's just lipstick on a pig, but at least it looks better. If you want to interoperate with other utilities that are provided by cygwin, use the cygwin perl and not ActiveState. Having both on your machine should work just fine, as long as you don't try to share anything between them. Treat them as completely different things (which they are). -- 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/