How do people envision running tcl module applications that have been
installed into a transparent/installation repository?  Besides the
obvious just run it.

 

The builtin tcl module stuff appears to only be looking at items under
the package directory.  The package side of things makes sense.  However
once you get applications installed, some with multiple versions, in
multiple architectures what mechanisms are in place, or planned, to
determine which application is the correct one to run.  For instance I
don't readily see a builtin way of getting the architecture that you are
currently on, same string anyways (ie linux-glibc2.3-ix86).  Also with
the version being incorporated into the filename it's not a straight
forward "add this directory to the PATH".  It would seem like you would
always be stuck updating some sort of startup wrapper to run these
applications, or creating a more intelligent wrapper to start these to
fit you needs.  An intelligent wrapper in some cases would not be much
different than the whole package tcl module mechanism only for starting
the latest version of a given application for your given architecture
via an exec.

 

I realize this is more up to the end user to decide on, but I'm curious
if there is more of a plan to this that we haven't been shown yet or if
I'm just blind to something more obvious.  Maybe I'm just looking at the
application end of a transparent/installation repository wrong?

 


NOTICE:  This email message is for the sole use of the intended recipient(s)=
 and may contain confidential and privileged information.  Any unauthorized=
 review, use, disclosure or distribution is prohibited.  If you are not the=
 intended recipient, please contact the sender by reply email and destroy al=
l copies of the original message.