It is fine if we just document somewhere
  a) one stack per machine or at minimum separate shells
  b how to work with multiple versions of a package

I guess qserv/README-devel.txt would be a reasonable
place for that.

Jacek



On 05/23/2014 01:19 PM, Kian-Tat Lim wrote:
> Jacek,
>
>> That sort of things can be dangerous, we need to find a way to prevent
>> it from happening.
>
> 	Common eups usage is to have one stack per machine with multiple
> versions of each package in the stack.  Having multiple completely
> separate stacks is unusual and not usually recommended.  If you do work
> with separate stacks, you need to do so from separate shells.
>
>> Also, I noticed that I can't work with both at the same time, I am
>> getting some sort of global lock collision.
>
> 	Aside from needing to work in separate shells, eups also keeps
> some state in your ~/.eups directory, which may cause problems when
> working with multiple stacks.
>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1