On Sat, 2009-08-15 at 09:00 +0200, leppie wrote: > ----- Original Message ----- > > > > 3. While I am not a great fan of Microsoft, getting things running on > > Windows is always a good thing; I even think native Windows Ikarus would > > be a good thing :-). To this end, there's no reason why one should use > > Unix-specific things when a more generic approach is almost as good. For > > example, zip doesn't compress as much as gzip or bzip2, but it's almost > > as good. Similarly, symbolic links don't work on Windows, so we can live > > without them. > > > > Windows does support symlinks out-of-the-box in Win2003 Server and Vista > onwards. See mklink. > > Unfortunately, bzr on Windows ignores it, and given an invalid Windows > filename (as present in Derrick's SRFI libraries*), it simply blows up.
> * I am forced to boot into a Linux VM to do a bzr update. Then I need to > compress it (tar.gz) and copy to Windows. Then it will only decompress > correctly if extracted within Cygwin. That sucks. Those symlinks exists only so I/we don't have to type/read "%3a" everywhere. But that's only relevant when working on the source-code, which is less frequent and less important. So, I suppose we should get rid of the symlinks and get used to "%3a", instead of inconveniencing Windows users (as much as I might personally like doing that in revenge for Microsoft helping ruin computing for the last decades; I blame Unix too, but at least it has symlinks :-) I'll get rid of them soon, unless people convince me not to. -- : Derick ----------------------------------------------------------------
