Generate rexipies in the Rexfile

[matt604-adjust]

I recently tripped over adding a new rexipe and it wasn't showing up in -T. I hadn't put it in the Rexfile as I missed that.

I don't think there is a reason not to include a rexipe in the master Rexfile. That being the case maybe we want to walk 'infrastructure/lib/Rex/Adjust' directory and include everything in there?

Cheers

m!

Module::Pluggable exists:

use Module::Pluggable search_paths => ['Rex::Adjust'];

Inserting this intelligently into Rex is the best idea, but looks it can just be shoved into the Rexfile in infra.git.

The maintainers would be interested in a patch that allows inclusion via module arguments, i.e., add a key and check for it in Rex's main import subroutine.

use Rex auto_import => 'lib/';
use Rex auto_import => qw(lib/);

[amaxine]

In essence, this works:

use Module::Pluggable require => 1, search_dirs => ['lib/'], search_path => ['Rex'], sub_name => 'tasks';
tasks();

But it breaks the current behaviour of needs when using it for tasks in other modules. As far as I can tell, using needs shouldn't require having use for each module used, or at least that's how it gets used.

Or we can break this bit and expect modules to be explicit about what they want?

How exactly does it break needs? Expecting modules to be explicit is a good thing.

[amaxine]

To have a written record, currently needs doesn't require explicitly requireing modules, and I found that others' modules, and especially our own, rely on this.

Of course this behaviour isn't really documented so one could argue we can just make the change, for the sake of having a simpler Rexfile, and being explicit about the needs of each module. I'd be broadly in favour of that clarity.