Am 28.02.2014 19:03, schrieb Richard Hughes:
On 28 February 2014 17:45, Rex Dieter <rdieter(a)math.unl.edu>
> 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.
There are a number of situations your system could cover, in order to
not fail by over simplifying.
Two sRGB profiles in one system is maybe a user decission. Like a user
installs original HP sRGB.icm profile, or that from Argyll or lcms or
the official ICC web site.
You can easily *hide* any profile duplicates. I did so in the past in
Oyranos, but later decided against it for the above reasoning. But that
are design goals and that's entirely colord's and its users decission.
Given that colord is installed by default only for GNOME and otherwise
colord or Oyranos is installed by user or distributor decission, there
are few parallel installs likely.
> Not sure why he continues to repeat FUD all over the place
I think you probably need to link to actual things I've said rather
than overarching statements.
I'm happy to work with you on specifications but I'm not
supporting an OS where one CMS is interchangeable with another when
the design goals are so different.
Irritating attitude for a free and open source software developer. Specs
and software go hand in hand. Different concepts are needed to see what
is inspiring or fits best. One example for that statement is your own
desire to improve over existing software by starting a new project: colord.