Re: Re: Problems creating Crypt::OpenPGP standalone exe

I've seen that ActiveState has stated that Crypt::OpenPGP fails all tests. From what I can tell though, it's because the test suite didn't bother to create the basic key files and location files.

I wouldn't rely on ActiveState's automated ppm buildstatus. All tests pass for me.

t/00-compile.....ok
t/01-util........ok
t/02-buffer......ok
t/03-3des........ok
t/04-armour......ok
t/05-packets.....ok
t/06-cipher......ok
t/07-digest......ok
t/08-compress....ok
t/09-config......ok
t/10-keyring.....ok
t/11-encrypt.....ok
t/12-sign........ok
t/13-keygen......ok
All tests successful.
Files=14, Tests=327, 16 wallclock secs ( 0.00 cusr +  0.00 csys =  0.00 CPU)

Since you're doing this on Windows, which version of Perl are you using (ActiveState or cygwin and which build)?

cygwin runs on windows but cygwin is not windows. When somebody says they're running perl on windows cygwin is not involved (its probably activeperl or at least activeperl flavored perl, never cygwin).

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Comment on Re: Re: Problems creating Crypt::OpenPGP standalone exe

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.