Bug 234356 - Mk/Uses/go.mk: Add support for building with mage
Summary: Mk/Uses/go.mk: Add support for building with mage
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Dmitri Goutnik
URL:
Keywords: feature, needs-qa
Depends on:
Blocks:
 
Reported: 2018-12-24 12:55 UTC by Volodymyr Kostyrko
Modified: 2019-11-02 21:09 UTC (History)
1 user (show)

See Also:
koobs: maintainer-feedback? (dmgk)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Volodymyr Kostyrko 2018-12-24 12:55:37 UTC
Hello.

I tried to bring postgres_exporter to ports but it uses Mage instead of make. Mage is already in ports, but required bits in Uses/go.mk to enable Mage usage are absent... I'm not even sure how this should be done correctly.

Can someone enable using Mage as a builder please?

Thanks in advance.
Comment 1 Tobias Kortkamp freebsd_committer 2019-11-02 20:47:22 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.
Comment 2 Dmitri Goutnik freebsd_committer 2019-11-02 21:09:02 UTC
(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.