proposal: tool to describe exact dependencies/build environment for plugins to be shareable

[pjebs]

Proposal Details

@LukeShu in his response found here https://www.reddit.com/r/golang/comments/b6h8qq/comment/ejkxd2k/

discusses issues he encountered using the plugin package in a real-world use case.

It would be good if there was a tool made or a command or flag in go build that spits out the EXACT dependencies and build environment that was used to build the plugin that the consumer of the plugin has to meet.

That will reduce the barriers of using plugins to create libraries to distribute to others. We can communicate it exactly to the user.

If it was a tool, ideally you can provide the actual library file and the tool would just spit out that information.

[thepudds]

See #63290 (comment) for one approach.

[seankhliao]

I believe go version -m is enough.