Re: cygwin ATE CPAN!!!

[syphilis]

cpan still re-creates '\cygdrive\d\photog\home.bpb\.cpan...' directory.

This is by running Strawberry's cpan.bat ??
If so, then there must still be some remnant of Cygwin in your system environment variables.
In a cmd.exe shell run

set >set.txt

Then search the generated set.txt for occurrences of "cygdrive".

Does it really matter what the name of the cpan build directory is ?

If you're going to have more than one perl on a machine I think it's a good idea to make sure that *none* of them are in the Windows system path.
If there's no perl in the system path when you install Cygwin (or msys/msys2 - which was probably more suited to your needs) then you'll know that there will be only the one perl in the path that Cygwin's (or msys') bash shell sets up, and that perl will be the perl that ships with Cygwin (or msys).
This also means that there is no perl in the cmd.exe shell's path when you open one up.
This leaves you free to prefix/suffix the path with additional perls (to either a cmd or bash shell) as you want.

Last time I tried it, the Strawberry Perl installer wanted to prepend Strawberry Perl (and gcc) to the system path.
Therefore the 6 versions of Strawberry that I have are installations of a "Portable" Strawberry Perl distro - as installing the "Portable" disatro doesn't mess with the system path.

If I want to run a particular Strawberry Perl I just have to doubleclick the portableshell.bat that shipped with that portable Strawberry Perl (in its top level directory).
If I want to use Cygwin's perl I just need to start Cygwin's bash shell.
If I want to use msys' perl (which is extremely rarely) then I just need to open up an msys' bash shell.
And if I want to start up one of the other 20 or so Windows perls that I have then I just have to open a cmd.exe shell and then add that perl to the path (for the life of that shell).

As far as I know:
It's to be expected that, for Cygwin, cpan will select its $ENV{HOME} as the location of the .cpan directory, whereas Strawberry's cpan will select a different ($ENV{HOMEPATH}) location.
(I'm not sure if msys or msys2 ship with perl - but it's $ENV{HOME} will be separate from both Cygwin's $ENV{$HOME} and Strawberry's $ENV{HOMEPATH}.)

Cheers,
Rob

[BrianP]

Rob, >> C:\sisyphusion\Image-Magick-6.89>perl t/montage.t ... >> Test 12, signatures do not match.

I just copied IM over from my dead install and it works. The errors for ExifTool were for some other language I do not read so I just installed it by hand. All is well!

When I Upgraded to the newer Strawberry, I did get the portable one. I think one user, one Perl, one GCC keeps things simple. If I need another GCC, I can use another user. But I like U65's idea even better, real Linux on a VM. When I dual boot to OpenSuse, the configure flies off the screen in a blur rather than crawling at umpteen seconds per line like with windoz on the same machine. The build is effortless. I may try a cross compile next time.

The thought of having Real Linux running under windoz is a pipe dream. cyg was never more than a half-fast, pale imitation of Linux that has greatly disappointed me all 4 times I have tried it over the past decade. Once it's X thrashed my window manager and I had to reinstall the os. It always seems to prey on the rest of the system. I wonder if msys2 would be more considerate. When adope finally breaks photoshop with on OTA update to force all users onto their rent-a-cloud, I am going to throw winders out the window once and for all!

Off to setup a VM...
B