Some modules do not work correctly when not run via the named perl executable within a full perl installation. In some cases you may be able to fix this in code that runs at the start of your executables and sets the environment to suit the module.
Code stubs are prepended to each script that is turned into an executable. In most cases the code stub will take the form of a BEGIN block. When writing a code stub, bear in mind that more than one code stub may be prepended to your scripts. Do not assume that your BEGIN block will be the first executed.
You can create specific code stubs to apply to specific versions of the module. When you create a new code stub you are prompted to enter a module version. You can enter a module version string or you can enter 'DEFAULT'.
When Cava Packager encounters the module, it determines which code stub version to use by taking the highest code stub version that is equal to or less than the module version. Comparison is done on a string basis. If no number match is found, Cava Packager will fall back to the code stub marked 'DEFAULT' if one exists.
You can create a single code stub that will apply to all versions of a module if you define its version as 'DEFAULT'.