Changes between Initial Version and Version 1 of Ticket #465


Ignore:
Timestamp:
12/13/09 14:45:09 (14 years ago)
Author:
geofft
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #465

    • Property Cc broder added
    • Property Milestone changed from to IAP 2010
    • Property Reporter changed from broder to geofft
    • Property Summary changed from printing-config wrappers don't always use LPROPT to come up with a coherent plan for debathena-printing-config

  • Ticket #465 – Description

    initial v1  
    1 If the arguments passed to lpr can be interpreted purely as CUPS arguments (such as if you just do `lpr -Pfoo`), then the arguments in LPROPT aren't inserted into the processed command-line arguments. 
     1Right now our lpr wrapper is a descendant of a descendant of a hack, solving lots of little use cases but with no particular overarching intention about what it's doing. While we shouldn't  forget about the edge cases we're supporting and break them in a rewrite (cf. #455), it's about time to have a clear design and spec for what it's doing rather than continuing its descent into feature creep. 
    22 
    3 See also RT:1098339 
     3As I see it the two main issues with the current setup is that user-visible behavior depends on users being aware of whether a queue is CUPS and LPRng and that answering questions about the behavior usually requires looking at the source. 
     4 
     5This includes: (some of the following are inspired by TODOs in the current printing-config lpr wrapper) 
     6 * Should we support the traditional LPRng arguments that Athena's used for years, e.g., -Zduplex (ticket #444)? Forever? 
     7 * Should we try to get these arguments upstream somehow, or is a cross-platform Athena lpr script that you can put early in your PATH sufficient? (Or do we not care for non-Athena platforms?) 
     8 * Should the LPROPT environment variable be supported? Currently if you are printing to a CUPS queue, and if passed to lpr can be interpreted purely as CUPS arguments (such as if you just do `lpr -Pfoo`), then the arguments in LPROPT aren't inserted into the processed command-line arguments (see also RT:1098339). We could desupport it, or support it all the time. 
     9 * How do you default to double-sided printing, etc., for all queues? In theory LPROPT is an answer, but converting LPRng args to CUPS ones in perpetuity is silly and prevents you from actually specifying default CUPS arguments. 
     10 * Are we keeping LPRng clients installed forever, or at some point will we say that if you want to print to an lpd printer, you should add a CUPS queue, and that Kerberized lpd printing is desupported (unless CUPS grows support for it)? (We can also keep the clients around while making lpr.debathena never call them.) 
     11 * Are we keeping Hesiod pcap entries forever? 
     12 * Are we keeping the "Print to LPR..." gtk backend forever? This saved me last week when some subtle BrowsePolling bug caused only three faraway printers to show up in the pick list, but this is a config change from upstream and one that I think we intended to be temporary. 
     13 * Can CUPS be made to zephyr (ticket #184) 
     14 * Can CUPS be made to have an equivalent of -Zbanner=?