K-T,
On 09/23/2014 08:59 AM, Kian-Tat Lim wrote:
>> 1) I setup qserv, (and scisql, xrootd and all that)
> 	If dependencies are defined right, you should only need to setup
> one thing (qserv).
See, I think the problem is that none of the Qserv devs really 
understand what it means for "dependencies defined right", or think it's 
too much of a hassle. The latter is unlikely, I think, because we've 
shown willingness to engineer around the non-eups-related hassles of 
constructing, building, and configuring 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.
Is there anyway to eliminate that (for a local stack)? I think Jacek and 
I would be much less confused if eups never tried to setup "current". 
Maybe a flag or option we could pass? I am already used to saying 
"eupspkg -er" with blind trust, without having any idea about what "-er" 
means or why we need it.

>> 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).
>
What I'm slowly learning is that an eups "tag" means a particular 
combination of component package versions. So the right thing for qserv 
is to stamp an eups tag across all packages that qserv depends on, for 
each merge to master on qserv. So, all qserv devs need to have the 
appropriate privileges and knowledge to do this, hence the process and 
the philosophy need to be documented. Recipes won't cut it, because they 
assume an understanding of what each step does.

-Daniel

########################################################################
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