I wanted to replace a standard that I had installed with/in pear with a development version from github that was in another directory. So I symlinked the standard directory to the development directory:
.../Standards/Symfony2 -> ~/Developing/Symfony2-coding-standard
This needed the requested changes.
Allow aliased standards via symlinks.
X-Ref: https://pear.php.net/bugs/bug.php?id=19417 - Configuration via symlinks is useful where you have a shared configuration and/or IDE integrations that do not allow to specify standard-paths (e.g. Phpstorm).
Thanks for another great patch.
Fixed bug #19448 : Problem with detecting remote standards. Note that…
… this reverts the changes from pull request #29, although the symlink issue that code was fixing appears to have now been fixed by other changes to CodeSniffer.php anyway.