Summary: | Mk/Uses/go.mk: Add support for building with mage | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Volodymyr Kostyrko <arcade> |
Component: | Ports Framework | Assignee: | Dmitri Goutnik <dmgk> |
Status: | Closed Works As Intended | ||
Severity: | Affects Some People | CC: | dmgk |
Priority: | --- | Keywords: | feature, needs-qa |
Version: | Latest | Flags: | koobs:
maintainer-feedback?
(dmgk) |
Hardware: | Any | ||
OS: | Any |
Description
Volodymyr Kostyrko
2018-12-24 12:55:37 UTC
This can be done in the postgres_exporter directly if needed by overwriting do-build and/or do-install. It does not need to be integrated in USES=go just to get one port to build. Note that www/gohugo also has a magefile but can be built just fine with USES=go as normal. I'd assume that postgres_exporter is no different. Anyway assigning to USES=go maintainer. (In reply to Volodymyr Kostyrko from comment #0) I don't know what mage is but github.com/wrouesnel/postgres_exporter doesn't need it for build, it build just fine by regular "go build ./cmd/postgres_exporter". So I agree with Tobias, regular USES=go should be enough for creating postgres_exporter port. |