Re: Standard OCIO Directories

Richard Shaw <hobbe...@...>

On Thu, Apr 12, 2012 at 7:20 PM, Brendan Bolles <bre...@...> wrote:
On Apr 12, 2012, at 2:09 PM, Richard Shaw wrote:

Is this configuration data static or is it expected to change over
time? If it may change then it should go somewhere in /var such as

Well, people may add configurations from time to time, but it won't be changing as often as the stuff that normally goes in /var, like logs and temp files.  Apparently Gimp looks for ICC profiles in /usr/share/color/icc, so that's why I suggested /usr/share/OpenColorIO.  It seems to fit the description of /usr/share having "architecture-independent data".  Interesting standards document on the subject here:
Then I think there's really 3 paths to worry about then.

1. Since users should never manually put anything in /usr/share (or
/usr for that matter) I would put stuff that comes packaged into

2. Configurations that are not user specific but also not packaged can
go in /usr/local/share/OpenColorIO.

3. Personal configurations can go in a ~/.OpenColorIO or ~/.ocio type
directory (or whatever path already exists?).

There might also need to be a little priority logic for conflict
resolution. I would say 3 should override 2 and 2 should override 1.


Join to automatically receive all group messages.