in reply to layout/configuration of deployed files
How about relative path of lib: "use lib '../lib/';
Have you tried freelancing/outsourcing? Check out Scriptlance - I work there since 2003. For more info about Scriptlance and freelancing in general check out my home node.
Also, as suggested any developer can change his own PERL5LIB env variable - and put the /my/dev/his-spot/lib as first thing. If you have someone naming modules as existing and widely used Perl ones ... you're screwed sooner or latter :)
You can always just make a new namespace and put new stuff there. As in CompanyName::* - so CompanyName::System (CompanyName/System.pm)
Have you tried freelancing/outsourcing? Check out Scriptlance - I work there since 2003. For more info about Scriptlance and freelancing in general check out my home node.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: layout/configuration of deployed files
by klassa (Acolyte) on Mar 02, 2011 at 19:56 UTC |
In Section
Seekers of Perl Wisdom