Primarily, consider cvs or svn or something similar to keep your versions of projects and libraries. Though it is not necessary, it is widely recommended.

I suppose you want to have two separated locations, one for libraries and one for project-specific files. In this situation, with respect of your need to have productional and development versions, I can see following directory structure:

~/projects/productional/perl-lib
~/projects/productional/project1
~/projects/development/perl-lib
~/projects/development/project1

[download]
The other idea is how to use proper libraries? In your project scripts, you can do something as

#standard modules
use FindBin ();

#to add proper dir:
FindBin::again();
use lib $FindBin::RealBin.'/../perl-lib';

#internal modules
use MyLibraryModule;

[download]
It causes usage of development library in development scripts and productional library in productional scripts. The last issue is How to change devel version to productional one? If you will use some versioning system, it will support it easily. Without versioning system, it is up to your head and hands to copy files in the right way.

In reply to Re: Separating Development and Release Modules by pajout
in thread Separating Development and Release Modules by Irinotecan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.