Hi Fabrice, I started playing with qserv eups-based install process and learning eups along the way. I just went through the first step by checking out u/fjammes/eupspkg branch and running install.sh script. I decided to look around for what eups does and how it arranges things. Looking at table files in instalation area I observed one interesting thing that I don't quite understand. Basically some table files have 'if' blocks that do not make much sense to me and some have unbalanced braces. Here an example of latter: === stack/ups_db/Linux64/qserv/6.0.0rc1/ups/mysqlpython.table === if (type == exact) { setupRequired(python -j system) setupRequired(mysql -j 5.1.65) } else { setupRequired(python system) setupRequired(mysql 5.1.65) } } # <----- extra brace??? envPrepend(PYTHONPATH, ${PRODUCT_DIR}/lib/python) ================================================================= and here is an example of strange ifs: === stack/ups_db/Linux64/qserv/6.0.0rc1/ups/luaexpat.table === # luasocket build file relies strongly # on lua 5.1 if (type == exact) { if (type != exact) { setupRequired(lua -j 5.1.4) setupRequired(expat -j 2.0.1) } } else { if (type == exact) { setupRequired(lua -j 5.1.4) setupRequired(expat -j 2.0.1) } else { setupRequired(lua 5.1.4) setupRequired(expat 2.0.1) } } ============================================================== I tried to read about this "type == exact" ifs in https://dev.lsstcorp.org/trac/wiki/EupsTips and it looks to me that table files that come from http://datasky.in2p3.fr/qserv/distserver/tables/ are not supposed to have those ifs, they are added when table files are installed. Maybe eups gets confused by the existing ifs in table files when it does installation? Cheers, Andy ######################################################################## 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