go.mod: switch to Go modules

[karalabe]

+341 −811,974 😝

Fixes #20226.
Fixes #20164.
Fixes #20342.

[r8d8]

#19605

[gballet]

LGTM on the pcsclite side

[fjl]

One thing I don't like about this change is that the debian source package content is no longer deterministic. As written, build/ci.go packages the entire go module cache, which could contain
arbitrary modules checked out locally. I think it would be better to move the invocation of go install -n ./... into ci.go and run it with a different cache directory, then copy that directory instead.

Alternatively, we could run go list to find the list used modules and only copy those.

[karalabe]

I assume Travis' go cache is empty initially so we surely only ship what's needed. Executing in a diff environment might break this invariant though indeed.

…

On Wed, Nov 20, 2019, 13:56 Felix Lange ***@***.***> wrote: One thing I don't like about this change is that the debian source package content is no longer deterministic. As written, build/ci.go packages the entire go module cache, which could contain arbitrary modules checked out locally. I think it would be better to move the invocation of go install -n ./... into ci.go and run it with a different cache directory, then copy that directory instead. Alternatively, we could run go list to find the list used modules and only copy those. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20311?email_source=notifications&email_token=AAA7UGI2KQQC36WQXRW4A43QUUQWDA5CNFSM4JOSWY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEERXQ7Q#issuecomment-555972734>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA7UGJXWTODNRKVVROQEWLQUUQWDANCNFSM4JOSWY4A> .