A simple question pertaining to config for applications.

Imagine you have an ISP that gives you a classic ftp area like one of these two: 

/home/yourhost/www
/home/yourhost/cgi-bin

[download]
... and you add: 
/home/yourhost/lib/perl
/home/youhost/scripts

[download]

I've added scripts, because I also have telnet access and I put all my modules in lib perl.

Right, here's the question:

What method do you use to minimise the ammount of updates required to each scripts and cgi scripts if this directory was to change.

More interestingly, there might be a test server or a development machine with different file system structures. So everytime there was a test or site update, a few things will change.

So, minimum change is what I'm up for.

Your thoughts wise ones.

--
Steve Marvell

In reply to favourite config method by marvell

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.