Date: Fri, 29 Sep 1995 11:11:26 +0100 (MET) From: Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: ports@freebsd.org Subject: Re: tcl-7.4 / tk-4.0 Message-ID: <199509291011.LAA16957@ghpc6.ihf.rwth-aachen.de> In-Reply-To: <199509290905.CAA00926@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Sep 29, 95 02:05:17 am
next in thread | previous in thread | raw e-mail | index | archive | help
Satoshi Asami wrote: > So I renamed them to libtcl74.so.1.0 > and libtk40.so.1.0, and added "74" and "40" to the -l lines of the new > ports...then it was pointed out to me that since the new ports > overwrite tcl.h and tk.h, we can't compile the old stuff unless we > revert the headers back. Ack. Better rename the old headers. The package writers will eventually upgrade to the newer Tcl/Tk versions. Maybe it's easier to fix the ports using 7.3/3.6 to include tcl73.h and tk36.h and link against libtcl73.so.1.0/libtk36.so.1.0 and wait for the upgrade. > Note that with the libtcl.so.7.4 and libtk.so.4.0 scheme, old programs > will still run, it's just that you can't compile them anymore with the > newer versions sitting around. Some ports could be replaced with their latest version which already uses 7.4/4.0 (e. g., ical). This is not a problem for tcl-only scripts (like tksol) because the wish interpreters are named differently by default. > One "solution" is to admit that this is not going to work and put a > big banner in red, green and purple that funny things will happen if > you try to compile the old ports with the new stuff instaled. I don't > think many people keep going back and forth compiling stuff, for > package building, I can live with a few top-down "make" runs with DUDS > and stuff. What is DUDS? BTW, tclX7.4 and BLT1.8 are out, which use the newer Tcl/Tk versions. tg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509291011.LAA16957>