On Tue, 9 Mar 2004, Lombard, David N wrote:
> > 1. New command: switcher-reload > > This causes switcher to re-load your current environment based on > your > > switcher settings. For example: > > > > $ which mpirun > > /opt/lam-7.0/bin/mpirun > > $ switcher mpi = mpich-1.2.3 > > $ which mpirun > > /opt/lam-7.0/bin/mpirun > > Now this is surprising to me. I would not expect the last line by > looking at what you did.
This is how switcher has *always* been -- the switcher command only changes your preferences, it does *not* change your current environment. It is very strongly documented this way. From the text:
----- Note, however, that {\em \cmd{switcher} does not change the environment of the shell from which it was invoked.} This is a critical fact to remember when administrating your personal environment or the cluster. While this may seem inconvenient at first, \cmd{switcher} was specifically designed this way for two reasons:
\begin{enumerate} \item If a user inadvertantly damages their environment using \cmd{switcher}, there is still [potentially] a shell with an undamaged environment (i.e., the one that invoked \cmd{switcher}) that can be used to fix the problem.
\item The \cmd{switcher} package uses the \cmd{modules} package for most of the actual environment manipulation (see \url{http://modules.sourceforge.net/}). The \cmd{modules} package can be used directly by users (or scripts) who wish to manipulate their current environment. \end{enumerate} -----
In fact, it would be very difficult to make it change your current environment -- there's a bunch of very sitcky technical issues involved.
Wait... I'm confused. Is this not what switcher-reload does??
> > $ switcher-reload > > $ which mpirun > > /opt/mpich-1.2.3/bin/mpirun > > The $(switcher-reload) step should have been executed by the first > switcher command above to honor the "principle of least surprise." I'm > not aware of any similar "commit" processing at the command line.
It would be really, really hard to do this.
I don't understand this either. Is it not just doing a switcher-reload as the last instruction? I thought we had a reason in the past to keep the two commands separate, but I can't remember it. In the absence of any reason, I share Dave's thoughts.
Jeremy
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
