Date: Sat, 24 Sep 2016 05:42:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212956] [PATCH] USES/go.mk, add GO_EXTRA_PACKAGES for multi-package applications Message-ID: <bug-212956-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212956 Bug ID: 212956 Summary: [PATCH] USES/go.mk, add GO_EXTRA_PACKAGES for multi-package applications Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: bsdports@kyle-evans.net CC: freebsd-ports-bugs@FreeBSD.org Keywords: patch Created attachment 175116 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175116&action= =3Dedit svn(1) diff of Mk/Uses/go.mk to add GO_EXTRA_PACKAGES I've ran into a golang application ([1]) that is actually composed of four different packages within its own repository, plus a couple of external dependencies. Currently, this makes for kind of an ugly situation where one would need to= put these into their proper ${GO_SRCDIR}/${PACKAGENAME} paths in order to prope= rly build, and it gets kind of messy. Additionally, the behavior for creating ${GO_WRKSRC} is out-right wrong because the repository is already package-aware. I'm attaching a patch that handles this situation a little better with a GO_EXTRA_PACKAGES var. If GO_EXTRA_PACKAGES is populated, then: * Make sure that ${GO_PKGNAME} is included -- for multi-package repositorie= s, this should *always* work as it's the only sane layout I can think of * In post-extract we assume/check that each package is currently living in ${WRKSRC}/src and symlink it into place if proper. [1] https://github.com/arduino/arduino-builder --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212956-13>