That's what I thought. However, since Avahi is not using the correct API's, wouldn't this problem continue to exist in CUPS 1.5 or is is there a planned work around?
The reason I ask is because it seems to me that this problem wont be solved until Avahi makes use of the correct API's.
That's what I thought. However, since Avahi is not using the correct API's, wouldn't this problem continue to exist in CUPS 1.5 or is is there a planned work around?
The reason I ask is because it seems to me that this problem wont be solved until Avahi makes use of the correct API's.