[Printing-architecture] colord profile per-user in CUPS server

Richard Hughes hughsient at gmail.com
Thu Apr 26 17:05:01 UTC 2012


On 26 April 2012 17:45, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> The description of colord inside CUPS server, including the comparision
> table, in my yesterdays presentation, hit pretty much the situation,
> and I feel none of my concerns have been dispelled:
> * colord configuration is time(session) dependent

No, not at all. If you install a profile system wide then it's
available for all users at login time.

> * contrary CUPS server organises jobs in print queues

I don't understand this point, sorry.

> * thus interference of colord in multi user sessions are likely

Can you describe what you mean by 'interference' please?

> * ICC Profile selection is largely undefined due to above reasons
> * That means colord+CUPS become hard and laborous to debug for users.
> All in all, the colord hook inside CUPS server appears to be a pretty
> problematic and orthogonal approach.

I guess that comes down to opinion. Also it's probably pertinent to
note that colord works in a very similar way to ColorSync. And also,
that colord is being used by hundreds of thousands of users on Linux
*right now* rather than being a concept.

> The two other presented configuration approaches integrate nicely into CUPS
> server. Thus the per queue ICC profile and per job ICC embeddeding into PDF
> OutputIntent are in my opinion much more robust, useable and maintainable
> for enterprise and professional support.

Please, how many more times... If you embed an output ICC profile then
it gets used rather than the profile used specified by colord. It's
not an either/or situation.

Richard.


More information about the Printing-architecture mailing list