On Fri, May 21, 2010 at 3:54 AM, David Lee <david....@ecmwf.int> wrote: > I get the feeling I'm overlooking something obvious, but I don't know what > it is. > > A typical UNIX application will be installed something like: > binaries: /usr/bin > man pages: /usr/man > config files: /etc > data;state: /var > > MakeMaker supports various "INSTALL...BIN..." and "INSTALL...MAN..." options > to adjust the locations of the "binaries" and "man pages" aspects of the > application. That's fine; I'm happily using those. > > But I can't see how to specify the "config files" and "data;state" aspects. > > Any thoughts on what I have missed? Or hints or good-practice-tips on how > to specify to MM the application's config and state directories?
Two separate issues: (1) telling your application where to put things and (2) telling MakeMaker where to put things. Many people seem to be finding that it's easier to use File::ShareDir to access non-code config or data files in a known location within the perl installation hierarchy. This frees you from having to worry about whether there is an 'etc' or 'var' directory on a user's system. E.g. on Windows or for a non-root user on a shared hosting environment. Module::Install or Dist::Zilla make it very easy to configure a Makefile.PL to install files from a 'share' directory in your distribution directory to the place where File::ShareDir expects to find them. --- David
