Kai-Uwe,<div><br></div><div> I think we might help define an answer ourselves by providing typical use-cases and then a test suite. </div><div><br></div><div>Edmund<br><br><div class="gmail_quote">On Tue, Feb 28, 2012 at 8:17 AM, Kai-Uwe Behrmann <span dir="ltr"><<a href="mailto:ku.b@gmx.de">ku.b@gmx.de</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 27.02.12, 14:44 -0800 schrieb Michael Sweet:<div class="im"><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> CUPS 1.6 will include colord support - Red Hat contributed the work to Apple and I am working on integrating that code along with the Avahi support.<br> </blockquote> <br></div> So far colord in CUPS appears to me orthogonal to CUPS' own device profile configuration. CUPS has a clear concept for static vendor supplied device profiles, which are defined per print queue.<br> <br> colord provides non static local user profiles independent to any queue or job without check. Due to this under-determined nature is is easy to find many scenarios, where colord in CUPS behaves undefined and risks bugs. How does you see that colord inside CUPS works in a maintainable manner?<div class="im"> <br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> ______________________________<u></u>______________________________<u></u>____________<br> Michael Sweet, Senior Printing System Engineer, PWG Chair<br> </blockquote> <br></div> kind regards<br><font color="#888888"> Kai-Uwe</font><div><div></div><div class="h5"><br> ______________________________<u></u>_________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/openicc</a><br> </div></div></blockquote></div><br></div>