About
wind&oil, Weblog
Syndicate:
Subscribe to a syndicated feed of my weblog,
brought to you by the wonders of RSS.
Projects:
www.behrmann.name
www.oyranos.org
ColourWiki
CinePaint
home :: oyranos :: oyranos_2007.11.27_2.zurueck
Tue, 27 Nov 2007
OpenICC executeables paths
The new Oyranos continues to evolves to a CMM framework. But where to store?
The already mentioned OpenICC directory proposal handles text and binary data,
but no active parts. I am now thinking about a good way for making plug-ins and
extensions possible. The idea is to define standard API's which can later be
implemented by various CMM's. As most binaries are highly architecture dependend
theire place must reflect this appropriately. Continuing the current sheme we
would get the /usr/lib/color/ + /usr/local/lib/color/ + .local/lib/color/
paths. For the later we had to skip the XDG_DATA_HOME variable as it points to
HOME/.local/share, which is not good for our need. After defining the base
paths we can append a cmm/ to make the use of the content obvious.
Oh, binaries are not covered by the XDG spec. What now?
A OPENICC_PATH variable with the above paths? Who will set this?
/oyranos | 0 comments | permanent link
TrackBack can ping me at: http://www.behrmann.name/wind/oyranos/oyranos_2007.11.27_2.trackback
Your Comment