Thanks for your help and ideas.
An excerpt out of my MANIFEST with the associated target directories would look kind of this:
bin/mybin => /usr/local/bin helper/foo_handler.pl => /usr/local/share/mymod/client/bin helper/bar_handler.pl => /usr/local/share/mymod/client/bin helper/baz_handler.pl => /usr/local/share/mymod/client/bin conf/standard.ini => /var/opt/mymod/scan_repo conf/foo.ini => /var/opt/mymod/scan_repo conf/bar.ini => /var/opt/mymod/scan_repo conf/mybin.conf => /usr/local/share/mymod/client/mybin.conf # or maybe with another directory # cf/mybin.conf => /usr/local/share/mymod/client/mybin.conf lib/My/Module.pm => /usr/local/share/mymod/lib
In my case I think abusing INSTALLSCRIPT and INSTALLBIN would do if I only had my 'mybin' and the helper scripts, but as you see I have to handle also the different config and ini-files with different locations.
So I think I get back to the PL_FILES strategy you suggested. I think that should be the most successful one.
I also thought about the File::ShareDir and File::ShareDir::Install modules, such as the anonymous monk mentioned, but there's the drawback that this is only for read only data and that scares me a little bit off this.
So thank you very much, I'll try it out :-)
In reply to Re^2: Module::Build's adding new filetypes in ExtUtils::MakeMaker
by vicdan
in thread Module::Build's adding new filetypes in ExtUtils::MakeMaker
by vicdan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |