Thanks. However, that is essentially option A: bite the bullet. It would have to go in every single test file and every single set up script. If I am going to use ExtUtils::Command::MM to back my makefile, I either need
- A compelling argument for why a makefile backed by Module::Build is not good enough. There is no need for Find::Bin+use lib when Module::Build backs the makefile. If it really is not good enough, I would be willing to bite the bullet.
- A solution that does not require me to hardcode Find::Bin + use lib in file after file. Eliya has proposed one solution but there are still some outstanding portability questions.
| [reply] |
If I am going to use ExtUtils::Command::MM to back my makefile, I either need: A compelling argument for why a makefile backed by Module::Build is not good enough.
Hmm, so you're writing your own Makefile (no .PL)?
That is the worst of all solutions :)
--Module::Build::Compat (see Module::Build users -- please use the "traditional" create_makefile_pl option)
++Module::Install
A solution that does not require me to hardcode Find::Bin + use lib in file after file. Eliya has proposed one solution but there are still some outstanding portability questions
Why is that a painful/unpleasant/unavoidable solution?
You only have to do it once.
You don't even have to do it manually :)
You can make it part of your template or automate it
There is even use inc 'Plagger'; which you can use outside of Module::Install
| [reply] |
| [reply] |