Re: What to tell Module::Build, and where?

[sundialsvc4]

Many folks deal with an analog of this same problem with regard to “shared-hosting plans” for websites. You're running as a non-root guest, in a shared environment along with hundreds or even thousands of other sites, and this environment is being updated from time-to-time (you hope...) by the ISP vendor. Meanwhile, the site-specific environment used by your website must be maintained. In addition, you want to keep mirrors of each site's environment on your own development machine:   even when the several sites that you're responsible for are completely different, you want to be able to manage them all with an easy rsync.

You'll find a wealth of existing information here if you search for keywords like “shared hosting” and “PERL5LIB,” and you should do that next. I think it will be much more helpful than anything I could repeat here.

I maintain each website that I maintain, from a separate login account on my own systems. Each one's bash-login script issues the export commands that the site's own Apache configurations will use. (Each site also has a local VirtualHost configuration as blahblah.dev and this is listed in /etc/hosts, but I digress.)

Anyhow, Perl offers a number of ways to configure the library search-order:   the hard-coded list in the Perl executable; site-wide configuration files; environment variables, and use lib. All of these prepend entries to the @INC list which is always searched front-to-back. Using any one of these methods or some combination, you can set up very specific environments. As you now see, it's a common thing to do. No, the error-messages are not the greatest, but you're certainly not the first person to be head-whacking about them.

Finally, one other footnote-observation:   I don't know if your distro's management software is written in Perl, but that too is a valid consideration. You probably don't want to touch the “global, system-wide” settings. You don't want to install your CPAN-stuff in the global location. All that you want to do is to be sure that when “you” run “your stuff,” always “your library settings” are the ones that Perl will pick up in “your” case.

[stiller]

Great! I found your A good summary of how to use Perl in shared-hosting environments and it's good, I'll aply that to my setup, and I will do more searces for related stuff.

But it does not adress the extra requirements of Module::Build? Or will Module::Build just work if my Config.pm is more complete?