Comment 34 for bug 81689

The http://wiki.bazaar.canonical.com/WindowsSymlinkSupport proposals are still rely on "we could not support" concept. What is wrong to call external executables to cover the case?
"mklink" does the creation and "dir" recognition whether file/folder is symlink and where it points to.

While external executables call is slower than API, it is better than not support windows as platform or cut-off the symlink feature as proposed early.