Relocatable or per-user extension directory?

Is your feature request related to a problem? Please describe. When distributing Ghidra internally, we install it in a non-writable, per-machine installation dir: /opt/ghidra. Users that want to install/develop extensions, need to make their /opt/ghidra/Ghidra/Extensions directory writable. This is not ideal, as we have packaged Ghidra into a Debian package and want to distribute it that way.

Describe the solution you’d like Similar to what IDA Pro already supports: An additional search path in the user’s local home directory to load Extensions from.

Suggested paths

• Windows %USERPROFILE%\\Local Settings\\Application Data\Ghidra\Extensions (note that this is non-roaming to avoid cluttering the user profile that travels with the user)
• macOS $HOME/Library/Application Supprt/Ghidra/Extensions
• Linux $HOME/.ghidra/Extensions

This would also enable to package Ghidra extensions as Debian packages and install alongside.

Describe alternatives you’ve considered A bind-mount that overlays <GhidraInstallDir>/Ghidra/Extensions with one of the the paths above.

Additional context If there is interest, I can have a stab at implementing this myself.

[ryanmkurtz]

Hopefully no one worked on this. I just submitted a PR for it.

[TheAifam5]

I’m really interested in this. Made a fork already and I will try to implement it but I can’t say for sure 😄