Joshua Hoblitt wrote:
I've taken a look at using Module::Pluggable to register configure steps. The simplest way to do this is to let Module::Pluggable search through the ./config directory. This requires renaming all of the .pl configure files to .pm because of hardwired assumptions in Module::Pluggable.
How do you get correct dependencies for the steps then?
This is a workable solution if there won't be a holy war over importing Module::Pluggable into the Parrot tree. How do people feel about this?
No problem here, if there are significan advantages when using it. leo
