Bug 164649 - dev-lang/tk-8.4.9 - tkConfig.sh not being modified
Bug#: 164649 Product:  Gentoo Linux Version: unspecified Platform: AMD64
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: tcltk@gentoo.org Reported By: nairb774@gmail.com
Component: Development
URL: 
Summary: dev-lang/tk-8.4.9 - tkConfig.sh not being modified
Keywords:  
Status Whiteboard: 
Opened: 2007-01-31 03:41 0000
Description:   Opened: 2007-01-31 03:41 0000
Inside the ebuild under the src_install function the lines:

sed -i \
                -e "s,^\(TK_BUILD_LIB_SPEC='-L\)${S}/unix,\1/usr/${mylibdir},"
\
                -e
"s,^\(TK_SRC_DIR='\)${S}',\1/usr/${mylibdir}/tk${v1}/include'," \
                -e
"s,^\(TK_BUILD_STUB_LIB_SPEC='-L\)${S}/unix,\1/usr/${mylibdir}," \
                -e
"s,^\(TK_BUILD_STUB_LIB_PATH='\)${S}/unix,\1/usr/${mylibdir}," \
                -e "s,^\(TK_CC_SEARCH_FLAGS='.*\)',\1:/usr/${mylibdir}'," \
                -e "s,^\(TK_LD_SEARCH_FLAGS='.*\)',\1:/usr/${mylibdir}'," \
                ${D}/usr/lib/tkConfig.sh

Does not happen and it dies silently (without 'die'ing).  This inhibits tix
from being installed.  This happens because on the amd64 platform the
tkConfig.sh is placed in: /usr/lib64/

The error (hidden in the output) is:

sed: can't read /var/tmp/portage/tk-8.4.9/image//usr/lib/tkConfig.sh: No such
file or directory

Reproducible: Always

------- Comment #1 From Brian Atkinson 2007-01-31 04:09:41 0000 -------
Created an attachment (id=108716) [details]
Fixed ebuild for tk-8.4.9

The file is the tk-8.4.9 ebuild modified to fix the sed problem.

------- Comment #2 From Jakub Moc (RETIRED) 2007-01-31 08:07:22 0000 -------
Please, attach a unified diff. Makes reviewing the changes hell lot easier.

------- Comment #3 From Brian Atkinson 2007-01-31 17:57:35 0000 -------
Created an attachment (id=108782) [details]
The unified diff

A simple:
wget -O - http://bugs.gentoo.org/attachment.cgi?id=108716 | diff -u
/usr/portage/dev-lang/tk/tk-8.4.9.ebuild -
;)

------- Comment #4 From Brian Atkinson 2007-02-09 01:47:25 0000 -------
Patch added so that this bug can be closed.

------- Comment #5 From MATSUU Takuto 2007-04-27 17:55:18 0000 -------
Fixed in cvs.