Greetings,
To paraphrase Blaise Pascal: please forgive the length of this post;
I haven't the Perl/MakeMaker knowledge to make it more concise.
I'm new to MakeMaker and this list, but I've searched the archives for a couple of
hours. I'm trying to use MakeMaker a little unconventionally, it seems,
to build/package an application with it's class libraries.
The application is a single executable (script) named 'ddnstool'.
It also uses three modules as class libraries. To keep things straight
the modules live a couple of levels down in an internal company namespace.
I've used h2xs to generate module skeletons. So a MANIFEST *exerpt* might
look something like this:
MANIFEST
Makefile.PL
bin/ddnstool
FOO/DDNS/Exceptions/Makefile.PL
FOO/DDNS/Exceptions/Exceptions.pm
FOO/DDNS/Graph/Makefile.PL
FOO/DDNS/Graph/Graph.pm
FOO/DDNS/Zonemaster/Makefile.PL
FOO/DDNS/Zonemaster/Zonemaster.pm
My goal is to get everything tied together and in the top-level
..../blib so that I can develop and test subsets then the full app.
The only way I've figured out to do this is to create fake
packages at the two intervening directory levels:
FOO/FOO.pm
FOO/DDNS/DDNS.pm
But I really don't want those to install to .../site_perl :o/
I tried WriteMakefile( DIR => [ 'FOO/DDNS/Exceptions', 'FOO/DDNS/Graph',
'FOO/DDNS/Zonemaster', ],
....
)
....and removed FOO/Makefile.PL and FOO/DDNS/Makefile.PL, but then I end up
with two separate blib trees: a $(TOP_LEVEL)/blib and a
$(TOP_LEVEL)/FOO/DDNS/blib.
Is there a reason the DIR attribute does not also cause the
appropriate '../../...' prepend magic to happen? I think in
this particular case it *might* be possible to hack (ugly)
MM->pasthru, but only because all three of the modules are at the
same depth in the directory tree.
Any tips?
Thanks....
