Next tickets have been discussed :

DM-622 :
========

- qserv-configure.py needs a dedicated option for migrating, by default 
qserv-configure.py will set-up a run-dir from scratch (for developers)
- improve management of qserv-run-dir in start/stop scripts :
     => put it in QSERV_RUN_DIR add more safety on instance execution, 
run it with the full path in order the user knows what instance he launch.
- put a client configuration copy in qserv_run_dir/etc/qserv-client.conf 
in order to duplicate it to user directory ~/.lsst/qserv.conf
     => we need to think to find a better solution (instead of having 
only one ~/.lsst/qserv.conf which may be confusing for several Qserv 
instances)
- could it be better to move qserv-testdata.py to qserv_testdata 
package? qserv-testdata.py is kind of useless without test data.
     => open a ticket to record it, and let it in the backlog for now.

DM-895 :
========

- use eups generated version number (example : 
u.fjammes.DM-622-g86a30ec72a) as QSERV_RUN_DIR is complicated because 
this number is eups-generated and would make Qserv configuration tool 
eups dependant. This requires more reflexion :
     * Do we want to depend on eups or not for development ?
     * How to prevent conflict between qserv and eups version numbers if 
we set-up our own solution ?
     => wait for use-case and experience

- -a said it in the README file

DM-862 :
========

- log4cxx, apr and apr_utils  : need Mario answer about tags.

DM-930 :
========

- write a qserv.table parser to generate eups distrib install commands

- Point "I am a bit confused by two distribution servers in README-devel 
when installing dependencies. When you install qserv with "eups distrib 
install qserv -r http://lsst-web.ncsa.illinois.edu/~fjammes/qserv" do 
dependencies also come from two servers, how is that handled? Does your 
private server redirects to http://sw.lsstcorp.org/eupspkg for some 
packages or is it handled by eups itself" is solved by previous feature.

- update the documentation (README-devel.rst) with :
"Be advised that eupspkg may generate different version numbers 
depending on whether the code has changed after checkout. For example it 
may generate version which looks like "master-g86a30ec72a" for freshly 
checked-out code but if you change anything in your repository it will 
generate new version "master-g86a30ec72a-dirty". You may end up with two 
versions of qserv installed, be very careful and remember to run "setup 
qserv" with the correct version number."

DM-666 :
========

- Andy thinks that using sconsUtils for detecting boost is all-right, as 
sconsUtils is LSST-standard. BoostChecker extra features (example : 
detecting non-eups installed and system boost libraries) could be added 
to sconsUtils in the future ?

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