Control: tags -1 +patch +pending
Hi Axel, and thanks for your bugreport,
Le lundi, 14 janvier 2013 12.31:37, Axel Beckert a écrit :
I guess that many people are happy about the existence of this package,
so am I. :-)
Glad you like it. To be honest, we'd be in a better situation if it wasn't
needed, but ohwell.
But from the long description it is unclear to me and my coworkers at
which point in the common CUPS 1.6 vs CUPS 1.6 scenarios this
package can or should be installed:
1) On the CUPS = 1.6 server so that CUPS 1.6 clients can browse his
printer list?
Yes, by using the old 'cups' protocol in BrowseLocalProtocols.
2) On the CUPS = 1.6 client so that it can browse the printer list of
CUPS 1.6 printer servers?
Yes, by using the old 'cups' protocol in BrowseRemoteProtocols.
3) On the CUPS 1.6 server so that CUPS = 1.6 clients can browse his
printer list?
No. The configuration has to happen on the CUPS = 1.6 client, see 2) above.
4) On the CUPS 1.6 client so that it can browse the printer list of
CUPS = 1.6 printer servers?
As I understand it, no, see 1) above.
Or even a completely different setup like some proxy machine which
queries the = 1.6 server and broadcasts its printers to 1.6 clients?
No no, not that I know. The cups-browsed daemon works by managing raw queues
on the cups instance that it has access to locally depending on network
events.
So please update the long descrption of that package accordingly to make
clear where the package should be installed and where not.
The next upload will have something along these lines:
.
cups-browsed is also useful with a CUPS = 1.6 client to allow the
latter to browse the printer list of CUPS 1.6 servers (by using the
old 'cups' protocol in BrowseRemoteProtocols).
.
cups-browsed is also useful with a CUPS = 1.6 server to allow CUPS
1.6 clients to browse its printer list (by using the old 'cups'
protocol in BrowseLocalProtocols).
Cheers,
OdyX
signature.asc
Description: This is a digitally signed message part.
