Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 123764
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Printing Team <printing@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Hal Engel <hvengel@astound.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 123764 depends on: Show dependency tree
Bug 123764 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-02-22 16:04 0000 
version bump.  lcms version 1.15 has been "stable" for about a month now.

------- Comment #1 From Hal Engel 2006-02-22 17:33:23 0000 ------- 
Just learned that version 1.15 breaks ABI compatibility and that all apps that
use it will need to be re-compiled when the new version is installed.

------- Comment #2 From Florian Steinel 2006-03-25 07:09:01 0000 ------- 
Jep, and the lcms.pc contains an bug:
In lcms.pc replace
includedir=${prefix}/include
with
includedir=${prefix}/include/lcms
(upstream SF-Bug #1458303)

------- Comment #3 From Hal Engel 2006-03-25 10:03:10 0000 ------- 
I have to disagree.  Many things will not build correctly is the header files
are in ${prefix}/include/lcms.  There are lots of little thrid party packages
the look for the lcms headers in the include directory and not the include/lcms
directory for which there are no ebuilds.

------- Comment #4 From Florian Steinel 2006-03-26 04:06:47 0000 ------- 
I don't understand.
The lcms.pc pkgconfig file should define that the include headers are at
$(prefix)/include/lcms
(thats the upstream bug), later on it says
Cflags: -I${includedir}
so there should be no problem for programs (and ebuilds there of) which make
use of pkgconfig.
Could you please tell me which programs breake because of the location change?
(I already know of EyeOfGnome.)
Thanks.

------- Comment #5 From Hal Engel 2006-03-26 11:31:03 0000 ------- 
There are two others that I can think of off the top of my head.  LPROF
currently will not build with lcms in $prefix/include/lcms and there is a color
managment plugin for GIMP that will not build.  

I have updated the SCons build scripts for LPROF to look in both
$prefix/include and $prefix/include/lcms.  I have already put this change in
CVS so that should not be a problem donw the road.  But there is the potential
for there to be lots of smaller things like the GIMP plugin that will not be in
the portage tree.  

The bigger issue for LCMS 1.15 is the ABI compatibility issue.  Version 1.15 is
the first version of lcms to fully support the ICC version 4 standard.  So at
some point users will want to start using it.  If a user upgrades lcms but does
not rebuild apps that use it then these apps will not work correctly but I have
found that it will not fail in ways that make the source of the problem
apparent.

------- Comment #6 From Pablo De Nápoli 2006-04-02 15:51:35 0000 ------- 
Configure.in files app-office/koffice_rc1 says that lcms-1.1.4
is buggy, so we should let the users upgrade.

------- Comment #7 From Stefan Schweizer 2006-04-02 16:05:20 0000 ------- 
I just bumped it, sync in an hour to get it.

Thank you for this bug.

------- Comment #8 From Pablo De Nápoli 2006-04-02 19:14:15 0000 ------- 
Thank you Stefan for your help!
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug