Jacek,
> 1) I setup qserv, (and scisql, xrootd and all that)
If dependencies are defined right, you should only need to setup
one thing (qserv).
> 2) then I setup qserv_testdata
You need to do this with "-t tag" or have current defined
properly or use "-j" or, preferably, "-k".
> 3) I run qserv-test-integration.py from qserv_testdata
> and I am getting: ImportError: No module named admin
> Why? because setup qserv_testdata is unsetting qserv...
>
> eups list qserv|grep setup
> u.jbecla.DM-207-gf8e7177d8d-dirty setup
>
> cd ../qserv_testdata/
> setup -r .
>
> eups list qserv|grep setup
> 2014_06.0 current b74 setup
You always get current for dependencies unless you say
otherwise.
> Does it have to be this convoluted?
It's not really *that* convoluted, and there are reasons for it.
Doing what (you think) you want would, I think, introduce other
complexities (like constantly updating dependency versions).
--
Kian-Tat Lim, LSST Data Management, [log in to unmask]
########################################################################
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
|