So, I am getting the point that taint, and later versions of Perl are trying to make it difficult to use relative paths for modules!

You may put it like that. It turned out that too many people get it wrong and catch security holes, so making it difficult (but not impossible) gives people a chance to ponder over other approaches.

If a website has more than one environment, then you need a plan anyway (again, nothing to do with taint mode) how you deploy and maintain the files in your different environments. There are many solutions for that, but I'd go for something like this: 

/home/myusername/somewebsite/prod/cgi-bin
/home/myusername/somewebsite/prod/lib
/home/myusername/somewebsite/prod/templates

[download]
with the same subdirectories for dev and test. So each environment has its own base directory, but below that they all have the same structure. Then it is indeed possible to use FindBin to detect which environment you're actually in (assuming you don't run a persistent interpreter like mod_perl).

my ($prefix,$website,$environment,$basedir);
BEGIN {
   $prefix = '/home/myusername';
   $website = 'somewebsite';
   use FindBin qw($RealBin);
   if ($RealBin =~ m!$prefix/$website/(dev|test|prod)/cgi-bin!) {
      $environment = $1; # This is now untainted!
      $basedir = "$prefix/$website/$environment";
   }
   else die "Bad or no environment '$1'";
}
use lib "$basedir/lib";
my $tt = Template->new({INCLUDE_PATH => "$basedir/templates"});
...;

[download]

The BEGIN block is needed to do the necessary calculations during the compilation so that the directory is available when use lib is processed.

Other alternatives include setting the environment as an environment (sic!) variable in the corresponding section of the web server config. Environment variables are tainted, so again you need to validate/untaint them.

In reply to Re^3: Using relative paths with taint mode by haj
in thread Using relative paths with taint mode by Bod

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.