Vincent, On 2013-06-20, at 11:05 AM, Vincent Lefevre <vinc...@vinc17.net> wrote: > On 2013-06-20 10:46:00 -0400, Michael Sweet wrote: >> Given that this is only a problem for users depending on the >> ServerName directive in client.conf, it seemed much more practical >> (and reliable) to have the user/administrator specify any version >> limitations there. > > The initial problem is that the user needs to guess what to put there > (and update it if the version of the server changes).
For the former, if it doesn't work use /version=1.1. As for updating it, you don't need to if all you ever use are PPD-based printers, which is quite likely if you are just using ServerName to point to a single server. > Having some "cupsversion" utility to output the version would be > useful for configuration and to be able to diagnose problems more > easily. but is of limited usefulness given that the supported IPP versions have changed exactly 3 times over the life of CUPS since 1998 (1.0 for CUPS 1.0.x, 1.x for CUPS 1.1.0 through 1.3.12, 1.x and 2.x for CUPS 1.4.0 and later) and CUPS 1.4.0 was released 4 years ago next month. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/12a5fd73-66c4-4274-97c8-7d8eac4f2...@apple.com
