[Bug 196806] print/cups-base: build fails if any option other than MDNSRESPONDER is selected

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196806

Chris Hutchinson <portmaster at bsdforge.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |portmaster at bsdforge.com

--- Comment #5 from Chris Hutchinson <portmaster at 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?= ${.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¢ on the matter. :)

--Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.