On Tue, Jun 1, 2010 at 7:12 AM, David Lee <david....@ecmwf.int> wrote:
> So in this context, putting config files (read-only), and especially putting
> data/state files (read/write), into the perl installation hierarchy seems
> inappropriate; the natural mindset for the application would be the
> traditional UNIX "/etc" and "/var" locations, plus or minus considerations
> such as "Linux Standard Base" (LSB) conventions.
>
> Hence my wondering whether, just as "INSTALLBIN" (and similar) default to
> LSB-like conventions and perspective (rather than within the perl
> installation hierarchy), there might be analogous "INSTALL*" variables for
> LSB-like config ("/etc"-ish) and data/state ("/var"-ish) locations.
These do not exist by default. (The INSTALLBIN targets come from the
Config module and are set during perl compilation and only
perl-relevant directories are there.)
There are two (maybe three) steps to what you want to do:
(1) customize the "make" action to put files into blib/etc and blib/whatever
(2*) (*optional) customize your tests to look in blib/etc and so on
for things needed during testing
(3) customize the "make install" action to copy from blib/etc to /etc
I'm more familiar with how to do that using Module::Build -- see the
Module::Build::Cookbook on search.cpan.org in these sections:
# Adding new file types to the build process
# Adding new elements to the install process
Hopefully, someone familiar with how to do this with MakeMaker will be
able to give you more advice. There may also be plugins for
Module::Install to do this, but I don't know of any, myself.
Another good place to ask questions like the ones you have is
#toolchain on IRC at irc.perl.org -- you'll get a cross section of
EU::MM, M::B, and M::I experts there.
-- David
