in reply to Placement of custom modules outside of home directory?

Hello mldvx4,

I never had the chance to do this but about the name I suppose everything is good as long the path tell you and others something, like: /usr/local/lib/perl5/custom_modules (maybe better path names will come out from other monks who work on lucky OSs)

You can be interested in how-to-change-inc-to-find-perl-modules-in-non-standard-locations and in perlfaq about PERL5LIB

> They are still under somewhat active development..

A separate path for them is mandatory in my opinion: you can have two paths dev and prod never touching the latter until you are sure all your tests (do you have tests, dont you?) passes.

L*

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Replies are listed 'Best First'.
Re^2: Placement of custom modules outside of home directory?
by mldvx4 (Hermit) on Aug 31, 2022 at 14:55 UTC

    Keeping the development version and the latest production version separate is a good point, and the tests too. Unfortunately there is not a way to do automated testing on most of it. It has gotten complex enough that at least a written checklist is warranted.