Cygwin, by default installs all in 1 directory -- you delete the directory and it is uninstalled.
However, if you choose a custom install, and put it in the root dir, it might be more complicated.
It doesn't tie into the windows sys dir, and didn't used to even touch the registry. The only thing it uses the registry for is to allow users to install multiple - separate copies (which most users don't need).
I've tried Strawberry perl, activestate's perl (very incompat w/standard perl env using cpan) -- can't say I've tried citrus though.
One thing that made me as pleased as punch, was when Cygwin went 64-bit. All of the cygwin-x64 environment is available in safemode ***AND*** in the recovery environment. But that's nothing to do with perl, so enough of that. ;-).
I just find the bash env more comfy to design from. I often start simple scripts in shell or perl in the shell, editing it on the command line, then moving to the visual editor (invoking vi or whatever), and then writing it to a file and moving on from there. Set the number option in Vim, and exec perl scripts in another win -- and see things side-by-side. Simple paradigm that works the same for me on Windows as on linux -- same tool chain. No special Graphics or IDE's to learn.. alot may depend on what tools he is used to, but cut/paste -- highlight text and it is "selected", and use a middle click to paste somewhere if all is under 'X' -- but if in windows, extra keyboard usage and cumbersome.
But I'm not on the latest cygwin -- I didn't have the time/energy to work around newer changes that my highly customized environment often ran up against. I have the same logins on my linux and windows server -- with the linux server hosting files and the user-authentication for my windows system via a samba based domain on the linux server. Now that would all be overkill, but the basics seem ... so basic.
| 