Date: Wed, 17 Feb 2016 20:04:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196806] print/cups-base: build fails if any option other than MDNSRESPONDER is selected Message-ID: <bug-196806-13-EsqMLPVykJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196806-13@https.bugs.freebsd.org/bugzilla/> References: <bug-196806-13@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=3D196806 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #5 from Chris Hutchinson <portmaster@bsdforge.com> --- (In reply to Tobias Kortkamp from comment #3) > I did some investigating on this. The problem still exists and seems to > surface when print/cups-base and print/cups-client have different options > selected for Zeroconf support. For example if cups-base uses AVAHI and > cups-client uses MDNSRESPONDER compilation will fail. I'm unsure how this > can be fixed. The split of cups into cups-base, cups-client, cups-image > makes this harder than it has to be. Shouldn't all the cups-* be children of print/cups-base ? eg; MASTERDIR?=3D ${.CURDIR}/../cups-base Where name/connection resolution options are *only* possible via it's master/parent: print/cups-base ? I'm sure that this route would prevent conflicting (M)OPTION choices. No? Just my 0.2=C2=A2 on the matter. :) --Chris --=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-196806-13-EsqMLPVykJ>