Bug 232116

Summary: print/cups: mdnsresponder option as avahi alternative
Product: Ports & Packages Reporter: Matthieu Volat <mazhe>
Component: Individual Port(s)Assignee: Tijl Coosemans <tijl>
Status: New ---    
Severity: Affects Only Me Flags: bugzilla: maintainer-feedback? (tijl)
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
Add MDNSRESPONDER option as AVAHI alternative. none

Description Matthieu Volat 2018-10-09 11:38:26 UTC
Created attachment 197963 [details]
Add MDNSRESPONDER option as AVAHI alternative.

Hello,

I've noticed that at some point during the 2.x live of the cups packages, only avahi support was kept when the project also allow to use mdnsresponder for printer detection.

Here is a patch to reintroduce this support in print/cups.

Portlint a bit angry with other aspects of the port, but i'd rather not touch these now:

print/cups# portlint 
WARN: Makefile: [20]: USE_* seen before USES.  According to the porters-handbook, USES must appear first.
FATAL: Makefile: license specified is GPLv2 LGPL20, but LICENSE_FILE specified is for GPLv2.
WARN: Makefile: "USES" has to appear earlier.
WARN: /usr/ports/print/cups/files/patch-cups_ipp.c: patch was not generated using ``make makepatch''.  It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format.
1 fatal error and 3 warnings found.

checkplist is happy:
print/cups# make check-plist
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
===> Checking for items in pkg-plist which are not in STAGEDIR
===> No pkg-plist issues found (check-plist)

Thanks!
Comment 1 Tijl Coosemans freebsd_committer 2018-10-09 12:37:49 UTC
The problem is that cups-filters only supports avahi (hplip too if I remember correctly), so I removed the option because there were users messing up their configuration.  I don't want to deal with such support requests again, so you'll have to come up with a very good reason why you need this.  Cups supports mDNSResponder because that's what they use on MacOS.  In the open source world Avahi is de facto the standard.
Comment 2 Matthieu Volat 2018-10-09 12:51:00 UTC
> The problem is that cups-filters only supports avahi (hplip too if I remember
> correctly), so I removed the option because there were users messing up their 
> configuration. 

Not sure the relation with cups-filter. Adding support in print/cups made my installation detect my workplace printer.

> I don't want to deal with such support requests again, so you'll 
> have to come up with a very good reason why you need this.  

I guess "I need it because I don't use/want avahi" won't cut it.

> Cups supports mDNSResponder because that's what they use on MacOS. In the 
> open source world Avahi is de facto the standard.

Ok, I see the point then.
Comment 3 Tijl Coosemans freebsd_committer 2018-10-09 13:00:12 UTC
(In reply to Matthieu Volat from comment #2)
What's the output of "avahi-browse -a"?  Doesn't that list the printer?