Date: Wed, 20 May 2015 13:15:49 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 179481] [patch] graphics/rubygem-rmagick: optional X11 Message-ID: <bug-179481-21402-Bnk8ZIg4O2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-179481-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-179481-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=179481 Josh C <josh.cepek@usa.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josh.cepek@usa.net --- Comment #4 from Josh C <josh.cepek@usa.net> --- This was an incorrect change has has now BROKEN builds for sites that define OPTIONS_UNSET+=X11 in the global make.conf. If you want to build without X11, this is the correct way. Maintainer, can you please revert this patch? The problem here is that compliant ports do not depend on "meta" packages like ImageMagick-nox11 because these ports already have the logic to build without X11 if THAT port has such a feature. As graphics/rubygem-rmagick does not itself have any X11 build options, the X11 flag needs to be changed in the pkg UNIQUENAME of ImageMagick, either using the syntax above to set it globally, or defining ImageMagick_UNSET+=X11 in make.conf. This change has resulted in duplicate origin errors if attempting to install graphics/rubygem-rmagick witih ANY other complaint port in the tree, as both graphics/ImageMagick AND graphics/ImageMagick-nox11 (the latter, incorrectly pulled in as a result of this unnecessary change.) Please let me know if further information is required. -- 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-179481-21402-Bnk8ZIg4O2>