Bug 32655 - xcin and libtabe ask for db3 (but is db-3 in Gentoo)
Bug#: 32655 Product:  Gentoo Linux Version: 1.4 Platform: All
OS/Version: Linux Status: CLOSED Severity: normal Priority: P2
Resolution: FIXED Assigned To: cjk@gentoo.org Reported By: palatis@gentoo.tw
Component: Ebuilds
URL: 
Summary: xcin and libtabe ask for db3 (but is db-3 in Gentoo)
Keywords:  
Status Whiteboard: 
Opened: 2003-11-03 14:24 0000
Description:   Opened: 2003-11-03 14:24 0000
xcin-2.5.3_pre2 and libtabe-0.2.5 are asking for db3, but db3 should was db-3
in Gentoo, so that xcin and libtabe are unable to find the header files and
refuse to configure.

workarounds are in attachments.

------- Comment #1 From Victor Tseng 2003-11-03 14:27:22 0000 -------
Created an attachment (id=20199) [details]
patched libtabe ebuild

maybe someone would like to add a -r1 after the version number.

------- Comment #2 From Victor Tseng 2003-11-03 14:28:53 0000 -------
Created an attachment (id=20200) [details]
libtabe patch to search for db-3

put the fine in
/usr/portage/app-i18n/libtabe/files/libtabe-0.2.5/libtabe_0.2.5_db3_db-3.patch

------- Comment #3 From Victor Tseng 2003-11-03 14:32:41 0000 -------
Created an attachment (id=20201) [details]
patched xcin-2.5.3_pre2.ebuild

maybe someone would like to add a -r1 after the version number, too.

------- Comment #4 From Victor Tseng 2003-11-03 14:33:53 0000 -------
Created an attachment (id=20202) [details]
xcin patch to search for db-3

put this in
/usr/portage/app-i18n/xcin/files/xcin-2.5.3_pre2/xcin_2.5.3_pre2_db3_db-3.patch

------- Comment #5 From Alastair Tse (RETIRED) 2003-11-03 16:27:37 0000 -------
thanks for the patches. i've added them to the existing version but didn't
bump the revisions because they didn't add any new feature to the ebuilds.

i've cleaned up the libtabe and xcin ebuilds as well, so it a little more
managable.

------- Comment #6 From Victor Tseng 2003-11-04 04:42:11 0000 -------
fix confirmed, bug closed.

------- Comment #7 From Paul de Vrieze 2004-03-26 12:34:18 0000 -------
*** Bug 32235 has been marked as a duplicate of this bug. ***