[golist] Issue #18: Golist should work without $GOPATH from any directory

[Robert-André Mauchin]

eclipseo reported a new issue against the project: `golist` that you are following:
``
$GOPATH is deprecated, we shouldn't use it anymore.
``

To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/18

[Elliott Sales de Andrade]

qulogic added a new comment to an issue you are following:
``
Might be possible with [tools/go/packages](https://godoc.org/golang.org/x/tools/go/packages), but I've read that it's much much slower since it tries to do a full module download. This might be mitigated by setting up a GOPROXY.
``

To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/18

[Nicolas Mailhot]

nim added a new comment to an issue you are following:
``
The download is a no-go since it will be blocked by CI/CD systems like `mock`.

It should be possible to avoid setting a build-specific `GOPATH` in golist, by importing directly the directories golist operates on, and taking other code from a static system `GOPATH`.

Setting the build-specific `GOPATH` is where most of the problems lie: you have to create a specific directory structure, before golist will even parse your files. The system `GOPATH` OTOH is harmless and fine.
``

To reply, visit the link below or just reply to this email
https://pagure.io/golist/issue/18