How to upgrade SVN on OSX 10.11 El Capitan With SIP enabled
Instead of changing a protected file, why not change your path so that the newer SVN is called by your scripts and users?

That's best practice since you don't control the OS but you control the environment. Second best would be disable SIP and overwrite the file you intend to, then re-enable SIP. The reason it's second best is it takes longer, needs you to learn SIP disable, and the next time Apple patches the tool, your work is undone.

Changing path doesn't get undone when Apple updates the OS. This is the same even before SIP:


How do I upgrade git on Mac OS X?
Use downloaded Git instead of preinstalled Git


Just replace git for svn in the examples above.