Date: Mon, 10 Feb 1997 20:56:18 -0800 (PST) From: asami@vader.cs.berkeley.edu (Satoshi Asami) To: chuckr@glue.umd.edu Cc: jkh@time.cdrom.com, plm@xs4all.nl, freebsd-ports@freebsd.org Subject: Re: tcl 7.6 & tk 4.2 Message-ID: <199702110456.UAA24291@silvia.HIP.Berkeley.EDU> In-Reply-To: <Pine.OSF.3.95q.970210172613.22577B-100000@protocol.eng.umd.edu> (message from Chuck Robey on Mon, 10 Feb 1997 17:30:38 -0500 (EST))
next in thread | previous in thread | raw e-mail | index | archive | help
* I really think the pain of making multiple tcl/tk versions coexist is
* really not worth the cost. Since the 8.0 upgrade is so major, I would be
This argument has been done in the past, let's not start it again.
Here's the scheme:
====
(1) Move remaining version-specific files (tk.h and tkConfig.sh) into
subdirectories ("include/tk4.1/generic" and "lib/tk4.1",
respectively).
(2) Add a new target "default", which creates the tk.h and tkConfig.sh
symlinks in regular places.
(3a) Make "post-install" depend on "default" if this is the default
version (i.e., 4.1 for tk, none for tcl).
(3b) Make "post-install" print out a message "Type `make default' if
you want to make this version the default" if you are not tk-4.1.
===
This is really quite simple. I'll be happy to import tcl-7.6, tk-4.2
and tcl/tk-8.0 if someone makes them do this. This will allow us to
"beta-test" future releases before they become the default.
Note that we are not planning to put old versions back, so everything
before tcl-7.5 and tk-4.0 will NOT be re-activated even if someone
changes them.
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702110456.UAA24291>