Bugzilla Bug 100269

The current ebuild for lcms installs the header files in /usr/include/lcms
which
is not the normal location for these files (should be /usr/include).  As a
result every application that has a denpendancy on lcms needs to be patched or
otherwise tweaked before it can be built.  I have build a number of things for
which there is no portage ebuild that are dependant on lcms (a GIMP color
management plugin and a color profile builder - lprof) and in both cases I had
to tweak the source code to get these to build because of the non-standard
location of the lcms headers. There is currently a significant effort underway
to bring color management to a broader range of open source systems and lcms is
one of the building blocks for this effort.  This will soon impact CUPS as
version 1.2 will have a dependancy on lcms and as more systems become color
managment aware it will impact a larger number of applications.   The result is
a significant number of ebuilds that are more complex than they need to be and
that are therefore harder to maintain.

Created an attachment (id=64321) [edit]
patch to correct the location of the headers

This patch should fix this bug. thanks for your report.

Yes this patch will fixes the lcms ebuild.  Hopefully this will now be applied
to all new lcms ebuilds.

Created an attachment (id=64393) [edit]
fixed patch for lcms

Use this patch instead... includedir was removed from econf

These changes were commited in lcms-1.13-r2 and lcms-1.14-r1. Please test the
packages. Reopen the bug if you notice some problem. Fixed Thanks