 |
 |
The difference between 3.3.6 and 4.4.2 is how trailing slashes are treated in any source or destination URL. In 3.3.6 all trailing slashes were incorrectly removed making it difficult to specify directories and generally produced strange results as compared to cp or scp. This error was corrected in the 4.x series but, as Gerard noted, produced different results between the two versions. Arguably, the 4.2 xrdcp is correct in the way it handles URL's with a trailing slash (well, except for one bug that will soon be corrected -- when automatic path creation is on and the final directory component does not exist). The 3.x xrdcp is blatantly wrong.
All that said, the question is whether we should allow selecting incorrect behavior for comparability's sake. That is not so clear since it's doubtful people actually specified URL's with a trailing slash using the old xrdcp as it would produce a weird result. I am not totally against it but question whether it is really needed in practice. If we do allow reverting to bad behavior then it would only be via envar (e.g. XRD_STRIPSLASH).
So, now that this is explained, what are people's thoughts on it?.
—
Reply to this email directly or view it on GitHub.
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