Right now when using remote, you must either have a local environment for compiling to the target, or enable a compile server for that.  But there may be cases where the remote targets are already capable of compiling stap modules themselves, and we could let them do so directly.

The user would still get to write their script locally however they like, and can also get the fanout of running it on multiple --remote targets at once.

This would have similar questions as the compile server as to what to ship from the user to remote -- at least the script and -I tapsets, and all the options except remote itself.  But this wouldn't have the same security considerations as the compile server, because --remote works as an authenticated user already.

A new --remote-compile option might be the trigger for this new behavior.