Bug#710735: cups: ambiguous ref to /etc/cups/lpoptions

[Brian Potkin <claremont102@gmail.com>]

severity 710735 wishlist
thanks


On Sat 01 Jun 2013 at 16:06:41 -0400, Sanjoy Mahajan wrote:

Thank you for your report, Sanjoy.

> [Same as closed Bug#463752 on former cupsys-client package]

So we will assign this to cups-client.
 
> I misinterpreted this statement in the manpage for lpoptions:
> 
>        When run by the root user, lpoptions gets and sets default options  and
>        instances for all users in the /etc/cups/lpoptions file.
> 
> I thought that, if root uses lpoptions, those options apply to the user
> ids listed in /etc/cups/lpoptions.  A few other packages that have that
> kind of behavior, although I admit that it's not common.
> 
> When I looked at the lpoptions file itself, I realized what the
> manpage meant.  To clarify, perhaps the man page should read:
> 
>        When run by the root user, lpoptions gets and sets default
>        options and instances for all users, storing the data in the
>        /etc/cups/lpoptions file.

I myself have no problem myself with the existing statement.

   . .  . , lpoptions "does something" in the /etc/cups/lpoptions file.

is the way I would see it. But I have sympathy with your version and it
might be marginally better. Arguing your case would be done at

   http://www.cups.org/str.php

Because of this and because it is an enhancement request I'm putting its
severity at wishlist.