How about BLAST_NORUN or nopro.
Tancredi Botto wrote:
>>Yes, this would be very helpful. However, I propose a name that
>>is more informative rather than just "PRO". What about
>>"BLAST_SESSION"?
>>
>>
>
>
>The voting polls are open... Then how about BLAST_RUN ?
>
>The name "pro" is transparent (at least to me) as usually systems
>had two copies of cernlibs in /cern/pro and /cern/new, where pro (which
>stands for "production") was the absolutely safe fall back.
>
>-tancredi
>
>
>P.S.
>I realize I have managed to live long enough not to remember of any
>cerlib update for a quite a stretch now...
>
>
>
>
>
>>Taylan
>>
>>On Fri, 16 Jan 2004, Tancredi Botto wrote:
>>
>>
>>
>>>Hi,
>>>coda session name and file name will change. Everything will be pro2004
>>>
>>>One comment: actually we should take this chance to stop hardcoding
>>>pro2003 anymore. The et_transfer, the root search path, init getters (and
>>>maybe a few other things) should set via the environment variable $PRO
>>>
>>>In this way (depending on your shell) we need only toggle one of these
>>>possible choices
>>>
>>>setenv PRO pro2003
>>>setenv PRO pro2004
>>>setenv PRO commis
>>>
>>>in the login file. For the blast account I plan to make $DATADIR/$ANALDIR
>>>dependent on the PRO variable.
>>>
>>>Users should make these changes in their environment as well (minimally,
>>>you should only have to set "PRO" in you login, and do that after CVS is
>>>updated and redownloaded in your account)
>>>
>>>
>>>
>>>
>>>
>>
>>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST