[Openicc] Gutenprint team requests CM-off for a print queue be provided as a maintained engineering facility.
edmundronald at gmail.com
Fri May 11 14:49:41 PDT 2012
Thank you for discussing our request.
If a PPD is present, I would prefer it to be PPD based, because it
would mean that if we copy the PPD across to another system the other
system will behave exactly the same. The big problem with print
debugging at the moment, in my experience is that one always misses
setting the right things in the GUI etc, and reproducing a state
exactly is hard, especially across systems.
If a PPD is not present, I a out of my depth, but I would insist on
clearly visible state and reproductibility, for the reasons above.
Please understand, this is not a "do once and print one target while
holding one hand above your head, and touching your toes with the
other", but rather a mode into which one locks the whole queue under
development, and spends days running tests, and one needs to know that
nothing strange happens when the hardware is turned on and off etc,
and that the state of the while system can be quickly saved out and
reproduced at a distant site. eg. I am in Europe, while Robert is in
the states, some of our best collaborators are in Russia etc.
> What about a CLI that allows you to "treat this as device color" on a per queue basis, that remains resident until explicitly returned to the default state?
> This can be used for devices for which there is no PPD.
> Can the existing colord ProfilingInhibit() API be levered by a CLI tool to do this per device? Per queue?
> Chris Murphy
> openicc mailing list
> openicc at lists.freedesktop.org
More information about the openicc