Dear all,
as you have probably noticed in my recent commits, xrootd 4.1
packages now provide xrootd 3.3.6 compatibility layer and should update
cleanly from 3.3.6. All the applications, both client-side and
server-side compiled against 3.3.6 should continue to work after update
without the admin having to change anything in the config files. XRootD4
daemons need to be explicitly requested in the sysconfig file.
I have tested all this on an EOS instance running xrootd 3.3.6 and
after uptade to 4.1.0 things continued to work fine. I would appreciate
if you could have a look and provide feedback.
All these changes should make it possible to finally push 4.1.0 into
EPEL. I have contacted Mattias already, and asked him to have a look too.
Have a nice weekend!
Cheers,
Lukasz
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
