@rough-waiter-82403 the context here was the go plugin was taken as a bit of greenfield to express more opinons - disallow custom target names, disallow custom source globs, force single source/3rdparty roots, etc. It may be that the latter breaks down in the face of real world go usage / export of go libraries to the outside world. Maybe some re-thought needed, but you'll need to guide things with your use-case / where Pants falls short.