My guess would be that you are.
Examine perl -V to be sure.
The easiest way to see binary incompatibility is by comparing libs (as in perl -V:libs)
and
usethreads=undef use5005threads=undef useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
I doubt you compiled with 64bits, without perlio, without ithreads or multiplicity ...
That should generally cover it, but it's best to just try it out.
It's also a good idea to run the test suite after downloading the PPM (to be really sure -- %90 success is good).
There is very little difference between "activeperl" and the official perl release, well, there is nothing that would spontaneously cause binary incompatibility given similar compile conditions (ActiveState releases a patch for the official .... )
| 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. |
| [reply] |