Note that the problem isn't just an academic one, or a topic relevant
only for home-grown applications. The activestate repository has several
applications already within it. And, of course, the most important
application - tclsh - is probably going to need the issue resolved at
some point (say when the latest 8.5 compiles are available in the
repository).  

Notice that teacup _would_ have been the first application ... Except
that, in the latest teacups, the problem was worked around by a
specialized built in update command.

Perhaps rather than have

 teacup update-self

 once the issue is addressed, that special case will no longer be
needed.

I've been thinking about this for a number of months, with no really
good solution. My initial thought was that an application should be
installed into the same directory as the tclsh, then later I thought
perhaps things should go into the same directory as teacup. Right now,
that latter choice is becoming more and more attractive to me. The
problem, of course, is when someone manages a repository containing code
for multiple platforms. Perhaps things should be installed like this:

Path/to/bin/
   Path/to/bin/binary-platform1/
   Path/to/bin/binary-platform2/
   tkcon_version1
   tkcon_version2
   other tcl scripts

Then, if the administrator so desires, they can create short cuts to
specific versions of tkcon, for example...

-- 
<URL: http://wiki.tcl.tk/ > 
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
<URL: mailto:lvirden@[...].com >  <URL: http://www.purl.org/NET/lvirden/
> 
 
_______________________________________________
TDK mailing list
TDK@[...].com
http://listserv.ActiveState.com/mailman/listinfo/tdk