Avoid CPAN Conflicts in Your Personal Perl Modules
How to keep CPAN from clobbering your personal and internal projects: Use the Local namespace for personal and internal projects.
Join the DZone community and get the full member experience.Join For Free
By convention, the top-levelPAUSE: On The Naming of Modules
Localnamespace should never conflict with anything on CPAN. This allows you to be confident that the name you choose under
Localisn't going to conflict with anything from the outside world.
Local::App::MyApp, whatever. This is also good advice for bespoke applications and libraries (the so-called DarkPAN) you're developing in-house. The last thing you need is to accidentally bring in (perhaps via dependencies) a module that gets loaded instead of yours.
Published at DZone with permission of Mark Gardner, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.