go ports fetching dependencies at build time

Herby G herby.gillot at gmail.com
Tue Apr 19 17:46:42 UTC 2022

The mechanism we use to vendor Go dependencies can be somewhat brittle and
does not work very well in a number of instances. For some updates, new Go
dependencies cause failures during extraction when attempting to capture
them in go.vendors.

Additionally, the key mechanism we currently use to vendor Go apps, which
is disabling Go modules (GO111MODULE=off) is not recommended.  We should
try to find a better solution. Gregory Anders proposed one a while back
which could vendor deps but still keep Go modules enabled:

On Tue, Apr 19, 2022 at 11:28 AM Ryan Schmidt <ryandesign at macports.org>

> Question regarding this commit:
> https://github.com/macports/macports-ports/commit/2c8bec5807d23120038f39d292a7e1cad625707d
> Here, a port tfmigrate was updated from 0.3.2 to 0.3.3 and changed to
> allow it to fetch dependencies at build time.
> What transpired between 0.3.2 and 0.3.3 that made it necessary to allow
> the port to do its own fetching again? This seems to happen to various go
> ports with some frequency. What can we do to improve the situation so that
> this does not become necessary so often?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20220419/e5ade359/attachment.htm>

More information about the macports-dev mailing list