[Openicc] Helping with colord

[Kai-Uwe Behrmann]

Am 08.03.11, 21:22 -0500 schrieb Robert Krawitz:
> On Tue, 8 Mar 2011 20:35:37 +0300, Alexandre Prokoudine wrote:
>> On 3/8/11, Kai-Uwe Behrmann wrote:
>>> Am 08.03.11, 12:02 +0300 schrieb Alexandre Prokoudine:
>>>> Oyranos? Not used in any software project any distribution relies on.
>>>
>>> Oyranos needs to convince projects.
>>
>> *sigh*
>>
>> That's another popular misconception. You don't make a successful
>> project by going around and convincing people. You arrange matters in
>> a way that *they* come to you and drool at your doorstep begging and
>> wagging their tails.
>
> Agreed, particularly for infrastructure projects.  For applications
> you can sometimes do things that appeal to a few people and push them;
> for infrastructure projects, it has to solve a common problem
> particularly well.

I think the monitor configuration part is solved in Oyranos in a 
automatic way. To set up Xorg with the _ICC_PROFILE(_xxx) atom is a 
important feature for Linux.

The two CMSes which bring colour management to non geek end users are 
the CUPS' cupsICCProfile for vendor supplied profiles. As Till suggested, 
it will be shipped rather soon.
The other one in this category are desktop colour servers like CompICC 
for instant colour correction of all non tagged display areas. Thats much 
like the PDF/PS DeviceXXX case handled by a opt out strategy. CompICC 
relies on Oyranos for the _ICC_PROFILE(_xxx) part.

[Cameras are almost sRGB tagged.
Scanners are hard with the current state of SANE. A ColorKeyWords 
equivalent is difficult to get distributed there. Patchs where proposed.]

>>> Any distributions can ship Oyranos already for that.
>>
>> Any distribution that wants extra work, because packaging Oyranos and
>> related apps is reportedly PITA.
>
> And yes, that's the other key point: it has to be easy to build,
> install, and use.  We've put a lot of work into ensuring Gutenprint
> will build easily on any POSIX-type operating system with minimal
> requirements, and we've taken a few extra steps to identify missing
> components (e. g. if you think you have CUPS installed but don't have
> the CUPS development package, it calls it out).  I like to think we've
> kept Gutenprint on the trailing edge of system requirements.

Hmm, reads like a suggestion to ship libXcm bundled with Oyranos.
Otherwise Oyranos is just POSIX together with some pretty standard 
components like libxml2.

Agreed about displaying the a filled/missed dependency summary at end 
of configure. (I remember once to have taken over that idea from 
Gutenprint, because it was so helpful.)


kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org