Recursive Script Discovery

[GreaterGoodest]

The script manager currently doesn't discover scripts in subdirectories of the provided bundle paths. This makes it a bit unwieldy to house large numbers of scripts in a repo. I know you can use category metadata to make them look nice in Ghidra itself, but it'd be nice to have them also be cleanly organized on disk.

Is this a conscious decision, or is this something that could be added as a selectable option?

[ryanmkurtz]

Yes, this was a conscious decision a very long time ago. I think a complicating factor is that Java uses subdirectories in its package layout, so if a top-level script wants to call into other classes that reside in a local package, they will need to be in a subdirectory.

[GreaterGoodest]

Would this still apply with the new PyGhidra functionality?

[ryanmkurtz]

Yea, the Script Manager and Bundle Manager didn't receive any major updates when we added PyGhidra, so it works the same way.

[GreaterGoodest]

In scenarios where a user's scripts wouldn't suffer from these import challenges, would it be feasible to add this as an "opt-in" toggle control that is off by default? It's something I'd be willing to dig into if there would be a possibility of it getting pulled.

[ryanmkurtz]

I'm struggling to to see how this would nicely fit in with the Script Manager's current behavior. It would likely be complex enough that we'd want to handle it internally rather than a PR.