Daniel,
> The new version isn't for the existing release qserv (I think it
> should work with the existing qserv, but it may not). Can we put the
> new xrootd version in without affecting the installation for
> 2014_05?
Yes. Manifests on the distribution server include strict
versions of all dependencies, so any given distribution package is
consistent and unaffected by other versions of its own or other
distribution packages.
> What else do I need to do to have my branch of qserv select the new
> xrootd version? I think I need to update the version in
> ups/qserv.table , but none of the existing dependencies require a
> version, so I'm not sure how to do this. Is there anything else I
> need to do?
You do not need to modify ups/qserv.table, but you do need to
have the appropriate version setup when you setup your qserv (either an
installed version or a "setup -r" version). There are several ways to
do this. One way is to declare the version you want to use most
commonly "current" in your stack. That will make it the version that is
automatically setup when no other version is specified. Another way is
to tag the version you want to use and use the "-t" option to setup.
--
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
|