Date: Mon, 11 May 2015 16:08:27 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 200129] [patch] www/rubygem-d3_rails Message-ID: <bug-200129-21402-sYIkjJionY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200129-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-200129-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200129 Johannes Jost Meixner <xmj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xmj@FreeBSD.org --- Comment #1 from Johannes Jost Meixner <xmj@FreeBSD.org> --- (In reply to Torsten Z=C3=BChlsdorff from comment #0) Good idea in theory. The problem is that, assuming you want to build Gitlab pkgs, this is not the right way to go - because the rubygem-d3_rails package will always be linke= d to railties3 by default. What you could do is, make the port into a master/slave structure -- rubygem-d3_rails, with a=20 RUN_DEPENDS?=3D rubygem-railties>=3D3.1.0:${PORTSDIR}/www/rubygem-railti= es and rubygem-d3_rails4, with an added PKGNAMESUFFIX=3D 4 RAILTIES4_RUN_DEPENDS=3D=20 rubygem-railties4>=3D4.0:${PORTSDIR}/www/rubygem-railties4 -- while keeping everything else equal. Then have GitLab depend on the d3_rails4 port, and packages can be built. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200129-21402-sYIkjJionY>