On 28 February 2014 17:45, Rex Dieter rdieter@math.unl.edu wrote:
I reverted the Conflicts pending some hopefully better solution forthcoming in: https://bugzilla.redhat.com/show_bug.cgi?id=1069672
Well, I still stand by my logic; the user does not want two *different* sRGB system profiles on one system and it's confusing to have both in dialogs to choose from. The alternative is that I *hide* at runtime any duplicate system profiles in the daemon.
Background: colord author Richard Hughes sees himself as a competitor to the elder Oyranos project, which helped paving the way for linux color management.
I don't care so much for age, but I do care about adoption and users of the API:
http://qa.debian.org/popcon.php?package=colord http://qa.debian.org/popcon.php?package=oyranos
colord does take some of the specifications you developed for Oyranos and extends them significantly. I'm not sure how that's relevant here.
Not sure why he continues to repeat FUD[1] all over the place regarding Oyranos.
I think you probably need to link to actual things I've said rather than overarching statements. I'm trying to help build a cohesive operating system which doesn't allow swapping of core parts of the system. I'm happy to work with you on specifications but I'm not happy supporting an OS where one CMS is interchangeable with another when the design goals are so different.
Richard.