From: Kevin W. <kw...@co...> - 2008-02-25 18:19:52
|
Jeff Hobbs wrote: > > No, currently ActiveTcl goes to the effort of _not_ overwriting the > native OS X version. However, that may change in the future, as the > ActiveState one is binary compatible, and much more recent. Does this mean that ActiveTcl would install in /usr/bin and /System/Library? That's a Bad Thing (TM). Apple strongly discourages the use of these directories by third-party developers. As others have noted, Apple updates might break your installation. It's also possible that ActiveTcl might break something unexpected, such as another program that depends on Apple-installed bits in those locations. (i.e. Apple's system installation of Python depends on Tk 8.4 for GUI apps, and will break if those binaries are updated to 8.5). The current method of putting third-party Tcl installations in /Library/Frameworks and /usr/local/bin is very sane, and I see no need to change it. Making sure that you are getting ActiveTcl is a simple matter of making sure your PATH points to /usr/local before /usr/bin. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com |