Request a Perl Module for Your Hosting Application

Posted on October 23rd, 2015

If a Perl application reports a missing module, identify the exact module name and the interpreter used by that application. A module installed for one Perl version or library path may not be visible to another.

What to include in a support ticket

  • The service/account and affected application, without account passwords.
  • The exact module name and trusted CPAN distribution or upstream reference.
  • The required version and the application’s Perl path/version.
  • The relevant sanitized error and any native-library/build dependencies.
  • Whether the module is needed only for your application or in a provider-managed runtime.

The older answer said requests were generally possible for CPAN modules. Do not read that as a guarantee that every module, build dependency or system-wide change is supported. Support must confirm availability and the appropriate scope for the actual plan.

Check without changing managed libraries

Where a panel offers a Perl module inventory, compare it with the application runtime rather than assuming the list covers every interpreter. An approved local library can be appropriate, but it must be configured for the application and maintained.

Do not overwrite panel-managed libraries or run arbitrary CPAN build scripts as root. Installation and module loading execute code; review provenance, dependencies and updates. Verify the application’s normal operation after an approved installation instead of treating a package-manager success message as proof.

Use the Perl documentation below to check module installation and interpreter options. On shared hosting, request the supported installation path through My InterServer rather than changing system Perl.

References

Perl module installation and local libraries; Perl interpreter and syntax-check behavior.