There are several ways to overcome this, depending on the platform, and whether perl is already installed on the target system.

For Windows environments, take a look at perl2exe from http://indigostar.com. It's not free, but there ain't no such thing as a free lunch.

If perl is already installed on the system, and there are no XS extensions in the modules that you are using, you can probably get away with including the modules in the archive kit, using paths relative to '.' You might want to make sure that '.' is included in the @LIB path (beware, security risk!)

If there are modules with extensions, you will need to make sure that binaries are available for all platforms of the target machine that you require. Then consider building kits for ActiveState PPM or RPM.

Hope this helps,

--rW