Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
It depends completely on how those scripts were written initially. If there are a low number of system calls and Perl modules were used that are available for Win32 environments (ActivePerl most likely) you should be OK. If you offloaded a lot of work to bash or C shell calls (not sure why you would) and did a lot of internal path jumping you will have a harder time. Trying them on a test repository under CVSNT to see what breaks is about your only option. Too many problem variables and coding styles to give a general answer. I would expect something to require fixing up which is just part of porting anything the first time. Under CVSNT you will almost certainly have to start your loginfo, taginfo and other calling CVS admin lines with the "perl" interpreter call, e.g. ALL perl myloginf.pl. Windows doesn't handle the #! syntax and other kludges to make perl.exe associate with .pl files haven't work well for me in the past. --Aric Aric Czarnowski Unimax Systems Corporation 612-204-3634 -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Josh Skains Subject: [cvsnt] Perl Scripts How hard is it to move my perl scripts from Linux to Windows if I decided to move my repository to a CVSNT on Windows? I use perl scripts to manage the tags and permissions. Thanks, JMS