Opened 18 years ago

Closed 18 years ago

#1897 closed task (fixed)

Tcl/Tk-8.4.13

Reported by: Randy McMurchy Owned by: Randy McMurchy
Priority: normal Milestone: 6.2.0
Component: BOOK Version: SVN
Severity: normal Keywords: Tcl Tk
Cc:

Description

Version increment to 8.4.13

http://sourceforge.net/projects/tcl

Change History (6)

comment:1 by Randy McMurchy, 18 years ago

Owner: changed from blfs-book@… to Randy McMurchy
Status: newassigned

I'm on the bubble with this update (many things link to tcl, but typically API/ABI doesn't change in minor rev releases). I think it is probably safe to update. Comments from others would be appreciated.

comment:2 by dnicholson@…, 18 years ago

Here's the release notes. It says it's mostly a bug-fix release. One bug that is fixed is the configure hack necessary with bash-3.1.

http://sourceforge.net/forum/forum.php?forum_id=564615

Anyway, I don't really use Tcl/Tk. My guess is that you're the editor that uses them the most. I'm leaning towards "do it", but I wouldn't really have to deal with the wreckage if anything happened.

comment:3 by bdubbs@…, 18 years ago

When doing this update, remember to look at bug #1860. We really should be in sync with LFS if at all possible.

Looking at the current instructions, the sed for configure in tcl is not needed any more.

Lets get rid of the environment variables. Use a local entity &v; in the instructions instead of $V. Use ${PWD} instead of ${DIR}.

There needs to be a note about test failures. I had one failure: cmdAH.test

I'm not sure the sed for tclConfig.sh is needed. Checking an old version of RH9 shows that they didn't think it was necessary. The third entry shows changing single quotes to double quotes, presumeably so the ${} will get translated by the shell, but there are several other places with the same construct that are not changed. It's curious why the develpers never noticed the problem.

In any case, it could be formatted as:

<!ENTITY v "8.4">

sed -i -e "s:${PWD}/unix:/usr/lib:" \
       -e "s:${PWD}:/usr/include/tcl&v;:" \
       -e "/TCL_LIB_FILE/s/'/\"/g" \
       tclConfig.sh

comment:4 by Randy McMurchy, 18 years ago

Everything looks good. Thanks, Bruce.

One thing though, I fail to see why it is important to be synced with LFS on a package that is not installed in LFS chapter 6. No big deal though, as they always update and we typically lag behind just a bit. I'm not sure there would ever be an instance where we would update tcl, expect or DejaGnu before LFS as they seem to get updates in quick (noted there is a huge difference in the amount of packages we/they have).

comment:5 by bdubbs@…, 18 years ago

Its just better to be consistent, but its not a blocker. BLFS does go into more detail so complete consistency is not possible.

comment:6 by Randy McMurchy, 18 years ago

Resolution: fixed
Status: assignedclosed

Updated BLFS to Tcl and Tk version 8.4.13. Also modified the build commands to not use any user-created environment variables. Noted no problems with the Tcl test suite.

Note: See TracTickets for help on using tickets.