From owner-freebsd-ports-bugs@freebsd.org  Wed Feb 17 20:04:16 2016
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF502AACF73
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Wed, 17 Feb 2016 20:04:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id AFF6D17A6
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 17 Feb 2016 20:04:16 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1HK4FjL071308
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 17 Feb 2016 20:04:16 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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
Date: Wed, 17 Feb 2016 20:04:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: portmaster@bsdforge.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2016 20:04:16 -0000

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.=