[cups.general] Passing extra information from environmenttobackend?

[Johannes Meixner]

Hello,

On Oct 23 09:21 Michael Sweet wrote (shortened):
> Johannes Meixner wrote:
> > On Oct 19 11:14 Michael R Sweet wrote (shortened):
> >> Kurt Pfeifle wrote:
> >>> What about a completely generic environment variable, which CUPS does
> >>> not at all use, but just faithfully passes down its filtering chain
> >>> through to the backend?
> >>
> >> How is that any different?
> > 
> > An environment variable can be set different for each process,
> > it keeps its value as long as the process runs, and it can be
> > automatically inherited by child processes.
> 
> Well, duh.  The issue is that options/attributes set via environment
> variable can interact with options passed by the app and/or on the
> command-line.

Of course.
And I fully agree with your other posting:

> No, we'd like to avoid setting print options from the environment -
> we already have enough problems with the default printer getting
> overridden...

I just liked to mention that there is a difference ;-)


By the way:
Because of the many ways where options can be set/stored I had to
make a confusing (and meanwhile a bit outdated) article:
http://en.opensuse.org/SDB:Print_Settings_with_CUPS


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex