John M. Dlugosz has asked for the wisdom of the Perl Monks concerning the following question:

I'm working with Catalyst, which uses the standard Perl system for building a tarball to deploy, which follows the same internal layout as a CPAN module. So, Catalyst doesn't itself document any of that. So I pose the question here, for general Perl community knowledge of these tools.

One of the files used by the program is AppName_local.conf, which if present overrides stuff in AppName.conf. The idea is to have different settings for the development environment. Now, I have more of a sliding scale, where the farther away I get from the dev directory I created it under, the less likely or often I am to use this file, but I can't say that I want it to never leave the original directory. But, the default on the real server should be that it is absent.

So, rather than excluding it from the MANIFEST (there is another file that lists things to simply leave out of the tarball), I want to rename it. It will be there, backed up and unforgotten, but dormant unless I rename it back.

How do I do that? Unlike exclusion, it's not a ready-prepared feature of the Makefile, to my knowledge. I suppose something needs to be added originally to the Makefile.PL file.

Can somebody help me out with a recipe?

Replies are listed 'Best First'.
Re: Something for Makefile.PL
by lamprecht (Friar) on Mar 25, 2011 at 09:14 UTC

    Why not rename the file, include (only) that in MANIFEST then create a symlink to it in the dev environment?

[reply]
      Nice idea! Thanks.
[reply]
Re: Something for Makefile.PL
by Khen1950fx (Canon) on Mar 25, 2011 at 11:45 UTC
    How about adding something like this to the Makefile.PL: 
    'META_MERGE'      => {
    no_index => {
        directory => [qw(AppName_local/AppName_local.conf)],
       },
    },

    [download]
    It'll be sitting in AppName_local until you're ready to use it.
[reply]
[d/l]

Back to Seekers of Perl Wisdom