Sean <seanlkml@xxxxxxxxxxxx> wrote: > On Wed, 18 Oct 2006 16:04:52 -0500 > Charles Duffy <cduffy@xxxxxxxxxxx> wrote: > > > Example time! > > > > There's a plugin for Bzr which adds support for Cygwin-compatible > > symlink support on Windows. (IIRC, this involves monkey-patching some of > > the Python standard library bits). > > > > Now, this is something which is *proposed* as a feature to be merged > > into upstream bzr, and it may happen at some point. That said, when I > > have a Windows-using coworker who wants to check out a repository that > > has symlinks in it (with his win32-native, no-cygwin-required bzr > > upstream binary), I don't need to tell him to go download and build bzr > > from a third party; instead, I just need to tell him to run a single > > command to check out the plugin in question into the bzr plugins folder. > > > > From an end-user convenience perspective, it's a pretty significant win. > > You'll need a better example than that. Git has supported a version > of Cygwin-compatible symlink support on Windows for quite some time. > And no plugins were needed. Actually I think the only part of that example that was really interesting was that Bzr runs natively on Windows and that Bzr's native method of extending the tool with additional features doesn't require Cygwin. Today Git doesn't run natively on Windows. It runs slowly through Cygwin, thanks to lots of various overheads in different places. And due to the crappy disk drive in my Windows box. :-) Today Git is typically extended (at least initially in prototyping mode) through Perl, Python, TCL or Bourne shell scripts. Although the first three are available natively on Windows the last requires Cygwin... and we've had some issues with ActiveState Perl on Windows in the past too. -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html